install-precommit
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.
Works with
--- 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. license: MIT --- You are helping the user install the pre-commit review hook. ## What This Hook Does The pre-commit review hook runs before every `git commit` and: 1. Shows files being committed with their status (added/modified/deleted) 2. Shows lines added and removed 3. Detects potentially sensitive files (.env, secrets, keys) 4. Detects debug statements (console.log, print, debugger, etc.) 5. Shows new dependencies being added 6. Shows TODOs being introduced 7. Requires user confirmation (y/n/d for diff) before proceeding This prevents "vibe coding" - blindly committing AI-generated code without understanding it. ## Installation Steps 1. **Check prerequisites:** - Verify this is a git repository (`.git` directory exists) - Check if a pre-commit hook already exists 2. **Create the hook script:** If `.claude/hooks/pre-commit-review.sh` doesn't exist, create it with the standard implementation. 3. **Install as git hook:** - Create `.git/hooks/` directory if needed - Copy or symlink the script to `.git/hooks/pre-commit` - Make it executable 4. **Verify installation:** - Confirm the hook is in place - Show the user how to test it - Explain how to bypass if needed ## Hook Script Source 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. ## After Installation Tell the user: 1. The hook is now active for all future commits 2. To skip the review (not recommended): `SKIP_PRE_COMMIT_REVIEW=1 git commit -m "message"` 3. To uninstall: `rm .git/hooks/pre-commit` ## Output Format ``` [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 ```
More Git Workflows skills
git-commit
github/awesome-copilot
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
git-workflow-and-versioning
addyosmani/agent-skills
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.
resolve-merge-conflicts
warpdotdev/common-skills
Resolve Git merge conflicts by extracting only unresolved paths, conflict hunks, and compact diffs instead of loading whole files into context. Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts, when `git status` shows unmerged paths, or when files contain conflict markers.
