
suggesting-cursor-hooks
When the user keeps asking for the same check to run (lint, tests, type-check), suggest a Cursor hook to automate it.
- Installs
- 479
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill suggesting-cursor-hooks- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads suggesting-cursor-hooks automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Suggesting Cursor Hooks
Watch for repeated manual requests. When the user keeps asking you to run the same command after changes, suggest a hook to automate it.
Triggers
Suggest a hook when you notice:
- The user asks you to run the same check 2+ times (e.g. "run lint", "run tests", "check types")
- The user says "always run X after editing" or "make sure to test after changes"
- You keep forgetting to run a validation step and the user catches it
- A CI failure could have been caught locally with a post-edit check
How to Suggest
You've asked me to run [command] after edits a few times. Want me to
set up a Cursor hook so it runs automatically?
If they say yes, create .cursor/hooks.json and the script:
{
"hooks": [
{
"event": "afterFileEdit",
"script": ".cursor/hooks/<name>.sh",
"pattern": "<glob>"
}
]
}
Common Hooks to Suggest
| User keeps asking... | Hook |
|---|---|
| "run lint" / "fix formatting" | afterFileEdit → eslint --fix or prettier --write |
| "check types" | afterFileEdit → tsc --noEmit on .ts/.tsx |
| "run tests" | afterFileEdit → run related test file |
| "don't touch .env" | beforeShellExecution → warn on secrets files |
| "make sure it builds" | stop → quick build check |
Rules
- Only suggest after a real repeated pattern, not preemptively
- Hook scripts must be fast (under 5 seconds) or the agent feels slow
- Scripts should exit 0 and report via stdout — don't block the agent unless the user explicitly wants that
- Check for existing
.cursor/hooks.jsonfirst — merge, don't overwrite - Keep it casual — "want me to automate this?" not a formal proposal
FAQ
What does the suggesting-cursor-hooks skill do?
When the user keeps asking for the same check to run (lint, tests, type-check), suggest a Cursor hook to automate it.
How do I install suggesting-cursor-hooks?
Run npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill suggesting-cursor-hooks in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/suggesting-cursor-hooks/ (personal) or .claude/skills/suggesting-cursor-hooks/ (project).
Which AI agents can use suggesting-cursor-hooks?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is suggesting-cursor-hooks safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains suggesting-cursor-hooks?
It is published by spencerpauly in spencerpauly/awesome-cursor-skills. It has 479 recorded installs.
More from spencerpauly/awesome-cursor-skills
visual-qa-testing
spencerpauly/awesome-cursor-skills
Visually QA a web application by launching it in Cursor's built-in browser, taking screenshots, checking console errors, and auditing network requests. Use after making UI changes to verify they look correct.
auditing-security
spencerpauly/awesome-cursor-skills
Perform a systematic security audit of a codebase, checking for OWASP Top 10 vulnerabilities, secrets exposure, and insecure patterns.
responsive-testing
spencerpauly/awesome-cursor-skills
Open the app in Cursor's browser at multiple viewport sizes, screenshot each, and report any layout breakage.
suggesting-cursor-rules
spencerpauly/awesome-cursor-skills
When the user repeats the same correction or convention multiple times, suggest a Cursor rule to encode it permanently.
systematic-debugging
spencerpauly/awesome-cursor-skills
Structured debugging methodology — reproduce, isolate, hypothesize, verify. Covers git bisect, binary search, logging, and minimal reproduction.
grinding-until-pass
spencerpauly/awesome-cursor-skills
Keep iterating on code changes until the tests pass, the build succeeds, or linting is clean. Runs in a tight loop of fix → run → check → repeat. Use when you want the agent to autonomously grind through test failures or build errors.
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work