hook-guard
Manage project hook-guard installation — set up, diagnose, or update Claude Code hooks, git pre-commit, and commit-msg scripts with security checks, code-quality gates, and CLAUDECODE skip logic. Triggers on "set up hooks", "configure pre-commit", "add linting hooks", "initialize hook-guard", "check hooks", "hook doctor", "verify hook setup", "troubleshoot hooks", "update hooks", "regenerate hooks", "sync hooks with current tools", or similar requests.
What this skill does
# Hook Guard Dispatch by user intent: - **Setup** — install is missing or user asks to set up / configure / initialize - **Doctor** — user asks to check / diagnose / verify / troubleshoot - **Update** — install exists and user asks to update / refresh / regenerate / sync If ambiguous: if `.githooks/pre-commit` exists and `.claude/settings.local.json` has hook-guard hooks → default to Doctor; otherwise → Setup. Read `references/settings.md` for the user-override schema (`.claude/hook-guard.local.md`) — applies to all three modes. --- ## Setup Skip if the user only wants to edit existing hooks. If `jj`-native only (no `.git/`), abort — pre-commit hooks not supported. 1. **Detect** — follow `references/detection.md`. Collect: languages, toolchain, VCS, existing hooks, monorepo. If existing hooks found, ask merge / replace / abort. 2. **Recommend** — read `.claude/hook-guard.local.md` if present. Present summary grouped by: CC hooks (PostToolUse lint/format soft, PreToolUse test gate hard), pre-commit always-run (security / integrity / structure), pre-commit skippable (lint / format / test), commit-msg. Ask to confirm. 3. **Generate**: - `.githooks/pre-commit` from `references/pre-commit-checks.md` — only enabled checks, real tool commands substituted. `chmod +x`. - `.githooks/commit-msg` from `references/commit-msg.md` if enabled. `chmod +x`. - `.claude/settings.local.json` — merge (not overwrite) hooks + `env.CLAUDECODE=1` per `references/cc-hooks.md`. - Run `git config core.hooksPath .githooks`. - Ensure `.claude/*.local.md` gitignored. 4. **Summary** — files touched, onboarding cmd (`git config core.hooksPath .githooks`), mention Doctor / Update modes. --- ## Doctor Run all checks, present a status table (✓ / ✗ / ⚠ / ℹ), then offer auto-fix for FAIL/WARN. 1. **`git config core.hooksPath`** — must equal `.githooks`. Unset = FAIL. Other = WARN. 2. **Hook files** — `.githooks/pre-commit` and (if conventional commits) `.githooks/commit-msg`: exist + executable. 3. **`.claude/settings.local.json`** — `hooks.PostToolUse` with Edit|Write matcher; `hooks.PreToolUse` with Bash matcher; `env.CLAUDECODE == "1"`. 4. **Tools** — grep pre-commit + CC hooks for tool names (ruff, eslint, prettier, gitleaks, jq, python3…); `command -v` each. 5. **CLAUDECODE skip** — `grep -q 'CLAUDECODE' .githooks/pre-commit`. Missing = WARN. 6. **Settings file** — validate `.claude/hook-guard.local.md` frontmatter (schema in `references/settings.md`); warn on unknown fields. 7. **(Optional) Dry-run** — offer to execute `.githooks/pre-commit` on current tree. Output ends with `Result: N/M checks passed`. Remediation: | Issue | Fix | |---|---| | core.hooksPath not set | `git config core.hooksPath .githooks` | | Hook not executable | `chmod +x .githooks/<file>` | | Tool missing | Suggest platform install | | CLAUDECODE skip / CC hooks missing | Re-run Setup | --- ## Update 1. **Verify install** — `.githooks/pre-commit` + hook-guard hooks in CC settings. Otherwise → Setup. 2. **Re-detect** — `references/detection.md`; read overrides from `.claude/hook-guard.local.md`. 3. **Diff** — parse existing pre-commit script + CC hooks; identify added / removed / changed tools or languages. 4. **Present** — diff-style summary; ask to confirm. 5. **Apply surgically**: - `.githooks/pre-commit`: replace only changed check-function bodies (canonical in `references/pre-commit-checks.md`); insert/remove checks in correct section; preserve structure, config vars, helpers. - `.claude/settings.local.json`: deep-merge; update only changed command strings; preserve unrelated settings. - Preserve user overrides throughout. 6. **Post-update** — summarize; suggest running Doctor.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.