القائمة
Install the pre-commit review hook that forces you to understand changes before committing. Use when you want to enable commit reviews or when setting up a new project.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | install-precommit |
| description | Install the pre-commit review hook that forces you to understand changes before committing. Use when you want to enable commit reviews or when setting up a new project. |
| tools | Read, Write, Bash |
| user-invocable | true |
You are helping the user install the pre-commit review hook.
The pre-commit review hook runs before every git commit and:
This prevents "vibe coding" - blindly committing AI-generated code without understanding it.
Check prerequisites:
.git directory exists)Create the hook script:
If .claude/hooks/pre-commit-review.sh doesn't exist, create it with the standard implementation.
Install as git hook:
.git/hooks/ directory if needed.git/hooks/pre-commitVerify installation:
The pre-commit hook script is located at .claude/hooks/pre-commit-review.sh.
Do NOT embed a copy here - always use the canonical version from the hooks directory. This ensures updates to the hook are applied everywhere.
If .claude/hooks/pre-commit-review.sh doesn't exist in the user's project, they may need to copy it from a template or create it based on their needs.
Tell the user:
SKIP_PRE_COMMIT_REVIEW=1 git commit -m "message"rm .git/hooks/pre-commit[OK] Pre-commit review hook installed
Location: .git/hooks/pre-commit
Source: .claude/hooks/pre-commit-review.sh
The hook will run before every commit, showing:
- Files being committed
- Lines added/removed
- Potential issues (sensitive files, debug statements)
- Requires your confirmation before proceeding
To test: stage some files and run `git commit`
To skip: SKIP_PRE_COMMIT_REVIEW=1 git commit -m "message"
To remove: rm .git/hooks/pre-commit
Start an autonomous implementation loop from a spec or PRD. Enters plan mode for user approval, enforces command gates (test/lint/typecheck/build), validates dependencies, commits incrementally, and maintains documentation and changelog. Production-ready quality gates.
Run a final release checklist before shipping. Verifies no TODOs, no debug code, docs updated, tests passing, dependencies justified, and security reviewed.
Document risks for changes touching auth, data, or migrations. Lists top risks, how to test/monitor them, and rollback strategy.
Maintain CHANGELOG.md with properly categorized entries. Use after implementing features, fixing bugs, or making any notable changes. Follows Keep a Changelog format.
Review code changes for quality, security, and best practices. Use when reviewing staged changes, pull requests, or specific files before merging.
Explain how code works in detail. Use when trying to understand unfamiliar code, complex logic, or system architecture.