Git Hooks Automation workflow skill. Use this skill when the user needs Master Git hooks setup with Husky, lint-staged, pre-commit framework, and commitlint. Automate code quality gates, formatting, linting, and commit message enforcement before code reaches CI and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Git Hooks Automation workflow skill. Use this skill when the user needs Master Git hooks setup with Husky, lint-staged, pre-commit framework, and commitlint. Automate code quality gates, formatting, linting, and commit message enforcement before code reaches CI and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/git-hooks-automation from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
Git Hooks Automation Automate code quality enforcement at the Git level. Set up hooks that lint, format, test, and validate before commits and pushes ever reach your CI pipeline — catching issues in seconds instead of minutes.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Git Hooks Fundamentals, Husky + lint-staged (Node.js Projects), pre-commit Framework (Python / Polyglot), Custom Hook Scripts (Any Language), CI Integration, Common Pitfalls & Fixes.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
User asks to "set up git hooks" or "add pre-commit hooks"
Configuring Husky, lint-staged, or the pre-commit framework
Automating linting, formatting, or type-checking before commits
Setting up pre-push hooks for test runners
Migrating from Husky v4 to v9+ or adopting hooks from scratch
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Read the overview and provenance files before loading any copied upstream support files.
Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
Validate the result against the upstream expectations and the evidence you can point to in the copied files.
Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.
Imported Workflow Notes
Imported: Git Hooks Fundamentals
Git hooks are scripts that run automatically at specific points in the Git workflow. They live in .git/hooks/ and are not version-controlled by default — which is why tools like Husky exist.
Hook Types & When They Fire
Hook
Fires When
Common Use
pre-commit
Before commit is created
Lint, format, type-check staged files
prepare-commit-msg
After default msg, before editor
Auto-populate commit templates
commit-msg
After user writes commit message
Enforce commit message format
post-commit
After commit is created
Notifications, logging
pre-push
Before push to remote
Run tests, check branch policies
pre-rebase
Before rebase starts
Prevent rebase on protected branches
post-merge
After merge completes
Install deps, run migrations
post-checkout
After checkout/switch
Install deps, rebuild assets
Native Git Hooks (No Framework)
# Create a pre-commit hook manuallycat > .git/hooks/pre-commit << 'EOF'#!/bin/shset -e
# Run linter on staged files only
STAGED_FILES=$(git diff --cached --name-only --diff-filter=ACM | grep -E '\.(js|ts|jsx|tsx)$' || true)
if [ -n "$STAGED_FILES" ]; thenecho"🔍 Linting staged files..."echo"$STAGED_FILES" | xargs npx eslint --fix
echo"$STAGED_FILES" | xargs git add # Re-stage after fixesfi
EOF
chmod +x .git/hooks/pre-commit
Problem: .git/hooks/ is local-only and not shared with the team. Use a framework instead.
Examples
Example 1: Ask for the upstream workflow directly
Use @git-hooks-automation to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @git-hooks-automation against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @git-hooks-automation for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @git-hooks-automation using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Staged files only — Never lint the entire codebase on every commit
Auto-fix when possible — --fix flags reduce developer friction
Fast hooks — Pre-commit should complete in < 5 seconds
Fail loud — Clear error messages with actionable fixes
Team-shared — Use Husky or core.hooksPath so hooks are version-controlled
CI as backup — Hooks are convenience; CI is the enforcer
Gradual adoption — Start with formatting, add linting, then testing
Imported Operating Notes
Imported: Key Principles
Staged files only — Never lint the entire codebase on every commit
Auto-fix when possible — --fix flags reduce developer friction
Fast hooks — Pre-commit should complete in < 5 seconds
Fail loud — Clear error messages with actionable fixes
Team-shared — Use Husky or core.hooksPath so hooks are version-controlled
CI as backup — Hooks are convenience; CI is the enforcer
Gradual adoption — Start with formatting, add linting, then testing
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/git-hooks-automation, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
assets/n/a
Imported Reference Notes
Imported: Husky + lint-staged (Node.js Projects)
The modern standard for JavaScript/TypeScript projects. Husky manages Git hooks; lint-staged runs commands only on staged files for speed.
pre-commit install # Install hooks
pre-commit run --all-files # Run on everything (CI or first setup)
pre-commit autoupdate # Update hook versions
pre-commit run <hook-id> # Run a specific hook
pre-commit clean # Clear cached environments
Imported: Custom Hook Scripts (Any Language)
For projects not using Node or Python, write hooks directly in shell.
Portable Pre-Commit Hook
#!/bin/sh# .githooks/pre-commit — Team-shared hooks directoryset -e
echo"=== Pre-Commit Checks ==="# 1. Prevent commits to main/master
BRANCH=$(git symbolic-ref --short HEAD 2>/dev/null || echo"detached")
if [ "$BRANCH" = "main" ] || [ "$BRANCH" = "master" ]; thenecho"❌ Direct commits to $BRANCH are not allowed. Use a feature branch."exit 1
fi# 2. Check for debugging artifactsif git diff --cached --diff-filter=ACM | grep -nE '(console\.log|debugger|binding\.pry|import pdb)' > /dev/null 2>&1; thenecho"⚠️ Debug statements found in staged files:"
git diff --cached --diff-filter=ACM | grep -nE '(console\.log|debugger|binding\.pry|import pdb)'echo"Remove them or use git commit --no-verify to bypass."exit 1
fi# 3. Check for large files (>1MB)
LARGE_FILES=$(git diff --cached --name-only --diff-filter=ACM | whileread f; do
size=$(wc -c < "$f" 2>/dev/null || echo 0)
if [ "$size" -gt 1048576 ]; thenecho"$f ($((size/1024))KB)"; fidone)
if [ -n "$LARGE_FILES" ]; thenecho"❌ Large files detected:"echo"$LARGE_FILES"exit 1
fi# 4. Check for secrets patternsif git diff --cached --diff-filter=ACM | grep -nEi '(AKIA[0-9A-Z]{16}|sk-[a-zA-Z0-9]{48}|ghp_[a-zA-Z0-9]{36}|password\s*=\s*["\x27][^"\x27]+["\x27])' > /dev/null 2>&1; thenecho"🚨 Potential secrets detected in staged changes! Review before committing."exit 1
fiecho"✅ All pre-commit checks passed"
Share Custom Hooks via core.hooksPath
# In your repo, set a shared hooks directory
git config core.hooksPath .githooks
# Add to project setup docs or Makefile# Makefile
setup:
git config core.hooksPath .githooks
chmod +x .githooks/*
Imported: CI Integration
Hooks are a first line of defense, but CI is the source of truth.
# Validate that lint-staged would pass (catch bypassed hooks)name:LintCheckon: [pull_request]
jobs:lint:runs-on:ubuntu-lateststeps:-uses:actions/checkout@v4-uses:actions/setup-node@v4with:node-version:20-run:npmci-run:npxeslint.--max-warnings=0-run:npxprettier--check.
Imported: Common Pitfalls & Fixes
Hooks Not Running
Symptom
Cause
Fix
Hooks silently skipped
Not installed in .git/hooks/
Run npx husky init or pre-commit install
"Permission denied"
Hook file not executable
chmod +x .husky/pre-commit
Hooks run but wrong ones
Stale hooks from old setup
Delete .git/hooks/ contents, reinstall
Works locally, fails in CI
Different Node/Python versions
Pin versions in CI config
Performance Issues
// ❌ Slow: runs on ALL files every commit{"scripts":{"precommit":"eslint src/ && prettier --write src/"}}// ✅ Fast: lint-staged runs ONLY on staged files{"lint-staged":{"*.{js,ts}":["eslint --fix","prettier --write"]}}
Bypassing Hooks (When Needed)
# Skip all hooks for a single commit
git commit --no-verify -m "wip: quick save"# Skip pre-push only
git push --no-verify
# Skip specific pre-commit hooks
SKIP=eslint git commit -m "fix: update config"
Warning: Bypassing hooks should be rare. If your team frequently bypasses, the hooks are too slow or too strict — fix them.
Imported: Migration Guide
Husky v4 → v9 Migration
# 1. Remove old Husky
npm uninstall husky
rm -rf .husky
# 2. Remove old config from package.json# Delete "husky": { "hooks": { ... } } section# 3. Install fresh
npm install --save-dev husky
npx husky init
# 4. Recreate hooksecho"npx lint-staged" > .husky/pre-commit
echo"npx --no -- commitlint --edit \$1" > .husky/commit-msg
# 5. Clean up — old Husky used package.json config,# new Husky uses .husky/ directory with plain scripts
Adopting Hooks on an Existing Project
# Step 1: Start with formatting only (low friction)# lint-staged config:
{ "*.{js,ts}": ["prettier --write"] }
# Step 2: Add linting after team adjusts (1-2 weeks later)
{ "*.{js,ts}": ["eslint --fix", "prettier --write"] }
# Step 3: Add commit message linting# Step 4: Add pre-push test runner# Gradual adoption prevents team resistance
Imported: Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
