Set up pre-commit hooks that lint and format staged files before each commit
Scanned 9/3/2026
Install to Claude Code
npx -y skills add black141312/ada --skill precommit --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Precommit?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/black141312-precommit)More formats (shields.io, HTML) on the badges page.
---
name: precommit
description: Set up pre-commit hooks that lint and format staged files before each commit
category: ci-cd
---
# Pre-commit
Reach for this to catch lint/format issues locally before they ever reach CI, keeping commits clean.
1. Pick the mechanism that fits the stack: `pre-commit` (framework, polyglot) or a JS-native combo of `husky` + `lint-staged`.
2. Add the config (`.pre-commit-config.yaml` or `package.json` `lint-staged` block) listing hooks: formatter, linter, and cheap checks.
3. Scope hooks to staged files only and run the same tools CI uses, so local and CI verdicts agree.
4. Install the git hook (`pre-commit install` or husky's `prepare` script) so it runs automatically on `git commit`.
5. Run the hooks across the whole repo once (`pre-commit run --all-files`) to surface and fix existing violations.
6. Document the one-line setup so a fresh clone installs hooks during `npm install` / bootstrap.
## Rules
- Keep hooks fast — only lint/format staged files; push heavy test suites to CI.
- Pin hook/tool versions so every developer runs identical checks.
- Make hooks fixable: prefer auto-formatters that re-stage, and give clear failure messages.
- Pre-commit is a convenience, not a gate — CI must still enforce the same checks (`--no-verify` exists).
- Ensure hooks install on clone (husky `prepare`) so they aren't silently skipped.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.