Intercept and block dangerous git commands before Claude executes them via PreToolUse hooks.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add mattpocock/skills --skill git-guardrails-claude-codeCompatible with
Supported agents
Blocks five command categories: git push (including --force ), git reset --hard , git clean , git branch -D , and git checkout / git restore on tracked files
Installs as a bash hook script to either project scope ( .claude/settings.json ) or globally ( ~/.claude/settings.json )
Customizable blocklist: edit the hook script to add or remove patterns based on your safety requirements
Claude r
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongit-guardrails-claude-codeExecute the skills CLI command in your project's root directory to begin installation:
epx add mattpocock/skills --skill git-guardrails-claude-codeFetches git-guardrails-claude-code from mattpocock/skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/git-guardrails-claude-code
Restart Cursor to activate git-guardrails-claude-code. Access via /git-guardrails-claude-codein your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
write-a-prd
mattpocock/skills · Productivity · same repo
no-mistakes
kunchenguid/no-mistakes · devops · 2 shared tags
ubiquitous-language
mattpocock/skills · Frontend · same repo
improve-codebase-architecture
mattpocock/skills · Productivity · same repo
web-artifacts-builder
anthropics/skills · AI/ML · tag: claude
theme-factory
anthropics/skills · AI/ML · tag: claude
git-guardrails-claude-code is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
git-guardrails-claude-code fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
git-guardrails-claude-code is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for git-guardrails-claude-code matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: git-guardrails-claude-code is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: git-guardrails-claude-code is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for git-guardrails-claude-code matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: git-guardrails-claude-code is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for git-guardrails-claude-code matched our evaluation — installs cleanly and behaves as described in the markdown.
git-guardrails-claude-code reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 46