commit-guard
/commit-guard
Format, lint, typecheck and test before a commit lands. Use when the task involves: commit, pre-commit, hook, staged, format, lint.
- Author
- Fate-Labs-CA ↗
- Repository
- estelle-plugins ↗
- Licence
- Apache-2.0
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Format, lint, typecheck and test before a commit lands. Use when the task involves: commit, pre-commit, hook, staged, format, lint.
Original author description
Format, lint, typecheck and test before a commit lands. Use when the task involves: commit, pre-commit, hook, staged, format, lint.
How it works
SKILL.md has no level-two headings · 14 lines, 163 words
SKILL.md preview
--- name: commit-guard description: "Format, lint, typecheck and test before a commit lands. Use when the task involves: commit, pre-commit, hook, staged, format, lint." user-invocable: false metadata: short-description: "Format, lint, typecheck and test before a commit lands." --- # commit-guard Check the exact change that will be committed. 1. Inspect the working tree and staged diff. Separate your files from other people's edits; never discard someone else's work to clean the tree. 2. Read the repository's required checks and run the formatter, linter, type checker, build and targeted tests that apply to this diff. Do not invent a universal command or coverage target. 3. Check that new files and required generated artifacts are included. Verify that tests ran the implementation that is actually staged. 4. Use `scan` on diffs touching credentials, user input, paths, queries or dependencies. Use `review` when correctness needs judgment. Resolve findings or record a justified limit. 5. Recheck status before committing. Commit only the intended paths, using the repository's conventions. 6. When a push is authorized, read the remote commit back before claiming it landed. A successful local command is not a remote receipt. Return the committed scope and checks that ran, naming skipped or failing checks.
Versions
The database has no other skills named commit-guard.
Database snapshot: 13.11.2026 · package version 1e9a75ecd3f3 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100setup-pre-commit
在当前仓库设置 Husky pre-commit hooks,集成 lint-staged (Prettier)、类型检查和测试。适用于用户想添加 pre-commit hooks、设置 Husky、配置 lint-staged,或在提交时运行格式化、类型检查和测试时。 - 100setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing. - 100commit
Format and commit only the user-authorized change set as one commit. Use when the user asks to commit. - 100pre-commit-review
Review staged and unstaged changes before committing. Use when asked for a pre-commit review, a code-quality review of the current diff, or when a solve workflow requests an independent review. - 100git-hooks-husky-pre-commit-lintstaged
Use this skill when enforcing linting, formatting, and unit tests before commit creation using Husky and lint-staged. - 98pre-commit-review
Run the required staged-diff review (a simplification pass, a secret scan, then four read-only review lanes) before every git commit, and record the approved staged-tree state for the shared Git hook. Use when an agent is about to commit, runs /pre-commit-review, reviews staged…