Skip to content
TrustedSkillsbeta
Back to all skills

Pre Commit Check

Checked
cartridge-gg·vlatest·backend

This tool automatically verifies code changes against predefined rules before committing, preventing errors and ensuring consistent quality.

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 cartridge-gg/controller --skill pre-commit-check -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

cartridge-gg

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 cartridge-gg/controller at b282b7b18d.

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

Commit
b282b7b18d
Manifest
.agents/skills/pre-commit-check/SKILL.md
Scanned
1 file, 28 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, pre-commit-check, likely automates checks before code commits. It's designed to ensure code quality and consistency by running predefined tests or linters as part of a commit process. This helps prevent errors from being introduced into the codebase and promotes adherence to coding standards.

When to use it

  • Enforcing Code Style: To automatically check for style violations before allowing a commit, ensuring consistent formatting across a project.
  • Running Linters: To execute linters that identify potential code quality issues and suggest improvements.
  • Automated Testing: To trigger basic tests or checks to verify the functionality of changes before merging them into a main branch.
  • Preventing Common Errors: To catch common mistakes, like missing imports or syntax errors, early in the development cycle.

Key capabilities

  • Automates pre-commit checks
  • Enforces code quality standards
  • Runs linters and tests
  • Prevents errors during commits

Example prompts

  • "Run a pre-commit check on this file."
  • "Execute all configured pre-commit hooks."
  • "Check for style violations before I commit these changes."

Tips & gotchas

This skill requires proper configuration of the pre-commit hooks and linters within your project's environment. Make sure you understand how to set up and manage these tools for optimal results.