Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →graniet/requesting-code-review
Pre-commit verification pipeline — static security scan, baseline-aware quality gates, independent reviewer subagent, and auto-fix loop. Use after code changes and before committing, pushing, or opening a PR.
Passed 13 of 19 test cases with the skill, and 12 of 19 without it.
and 3 more in the full report
5 fixed12 passed either way4 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
All security checks, baseline tests, and subagent reviews have passed cleanly. Write the exact command to commit all staged changes with description 'add user OAuth support'.
| Checked | Without skill | With skill |
|---|---|---|
| Includes the prefix [verified] at the start of the commit message. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill is repo-local and stays inactive until explicitly activated.
When the original instructions refer to legacy tool names, use these Kheish mappings:
terminal => bashweb_extract => web_fetch, plus web_search when discovery is neededsearch_files => grep_search and glob_searchbrowser_* tools require a browser-capable surfaced tool or MCP; if none is available, use the closest available surface and say so explicitlyWhen the instructions mention local helper files, resolve them from ${KHEISH_SKILL_DIR}.
Automated verification pipeline before code lands. Static scans, baseline-aware quality gates, an independent reviewer subagent, and an auto-fix loop.
Core principle: No agent should verify its own work. Fresh context finds what you miss.
git commit or git pushSkip for: documentation-only changes, pure config tweaks, or when user says "skip verification".
This skill vs github-code-review: This skill verifies YOUR changes before committing.
github-code-review reviews OTHER people's PRs on GitHub with inline comments.
git diff --cached
If empty, try git diff then git diff HEAD~1 HEAD.
test cases passed, vs 12 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.