Skip to content
TrustedSkillsbeta
Back to all skills

Pre Commit Checks

Checked
azure·vlatest·backend·MIT

Automates code quality checks before commits, preventing errors and ensuring consistent standards for smoother development workflows.

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 azure/azure-sdk-for-net --skill pre-commit-checks -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

azure

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 azure/azure-sdk-for-net at a9bc7e869d.

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

Commit
a9bc7e869d
Manifest
.github/skills/pre-commit-checks/SKILL.md
Scanned
1 file, 107 lines
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

This skill automates checks before code is committed, ensuring adherence to coding standards and preventing potential issues. It helps maintain code quality by running linters, formatters, and other validation tools as part of the commit process. This reduces errors and improves overall project consistency.

When to use it

  • Enforcing Code Style: When a team wants to ensure all contributions adhere to a specific coding style guide (e.g., consistent indentation, naming conventions).
  • Preventing Common Errors: To catch syntax errors or potential bugs before they are introduced into the codebase.
  • Automating Formatting: When you want to automatically format code according to established standards, saving developers time and effort.
  • Maintaining Project Health: As part of a continuous integration/continuous delivery (CI/CD) pipeline to proactively identify and address issues early on.

Key capabilities

  • Runs pre-commit hooks
  • Automates checks before code commits
  • Enforces coding standards
  • Provides automated formatting

Example prompts

  • "Run the pre-commit checks."
  • "Execute all configured linters."
  • "Format the current file according to our style guide."

Tips & gotchas

This skill requires a properly configured .pre-commit-config.yaml file in your project repository. Ensure that the necessary dependencies for the hooks are installed before using this skill.