Skip to content
TrustedSkillsbeta
Back to all skills

Git Precommit

Checked
u9401066·vlatest·backend·Apache-2.0

Automates git pre-commit checks like linting, formatting, and testing to ensure code quality before commits.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add u9401066/med-paper-assistant --skill git-precommit -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

u9401066

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned u9401066/med-paper-assistant at 7e1eab0b05.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
7e1eab0b05
Manifest
.claude/skills/git-precommit/SKILL.md
Scanned
2 files, 244 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The git-precommit skill automates pre-commit hooks to ensure code quality and consistency before committing changes. It runs configured checks, such as linting and formatting, preventing problematic code from entering the repository. This helps maintain a clean and consistent codebase by enforcing coding standards automatically.

When to use it

  • Enforcing style guides: Ensure all team members adhere to project-specific coding styles (e.g., Python's PEP8).
  • Preventing common errors: Catch syntax errors, formatting issues, or potential bugs before they are committed.
  • Automating code checks: Reduce manual review effort by automatically running linters and formatters on every commit.
  • Maintaining repository health: Keep the codebase clean and consistent over time, reducing technical debt.

Key capabilities

  • Automated pre-commit hook execution
  • Configurable check suite (linting, formatting)
  • Enforcement of coding standards
  • Prevention of problematic code commits

Example prompts

  • "Run the git pre-commit checks on this file."
  • "Execute the configured pre-commit hooks before committing these changes."
  • “Can you show me what the pre-commit hook configuration is?”

Tips & gotchas

The skill requires a properly configured .pre-commit-config.yaml file in the repository root to define the checks to be performed. Ensure this file exists and contains valid configurations for the desired tools.