code-kit

Plugin code-kit from marketplace tansuasici in tansuasici/claude-plugins. Commands read from the repo's manifest — 2 days ago.

Skills (40)

• accessibility-audit

  Audit UI code for WCAG 2.1 AA compliance — semantics, keyboard navigation, color contrast, and ARIA. Use when auditing accessibility or the user mentions a11y, screen readers, WCAG, or keyboard support. For visual/design quality use /design-review instead.

• architecture-review

  Review codebase architecture for SOLID violations, dependency health, module boundaries, and structural issues. Use when assessing whole-system structure or coupling. For single-module depth use /deepening-review; for a concrete refactor plan use /refactoring-guide.

• capabilities

  Summarize what the kit makes available in this project — user-invocable skills, review agents, active hooks, and enabled modules — as a one-shot onboarding briefing read live from disk. Use when you start in a kit-enabled project or ask "what's available here / what can I do". Do NOT use for install

• code-quality-audit

  Audit code for smells, error-handling gaps, and maintainability issues with actionable fixes. Use for a general code-quality pass not tied to project rules. To audit against the project's golden-principles.yaml use /quality-audit instead.

• constitution

  Author or extend the project's golden-principles.yaml — interactively for new repos, or by inferring and confirming candidates from existing code. Use when defining project coding principles or quality gates. Pairs with /quality-audit, which reads the file.

• dead-code-audit

  Detect unused code — unreferenced functions, dead imports, orphan files, and unreachable branches. Use when hunting dead code before a cleanup or release, or when the user suspects code is unused.

• debug

  Systematic root-cause debugging with evidence-before-fix enforcement and regression-test generation. Use when chasing a bug, failing test, error, crash, or unexpected behavior — before attempting a fix.

• deepening-review

  Surface shallow, pass-through modules as deepening candidates, then grill the chosen one interactively (Ousterhout depth/seam paradigm). Use when modules feel thin, fragmented, or hard to navigate. For whole-system structure use /architecture-review.

• dependency-audit

  Audit dependencies for security vulnerabilities, outdated versions, license risks, and bloat. Use when reviewing third-party packages, before a release, or when the user asks about CVEs, updates, or supply-chain risk.

• design-review

  Review UI implementation for design consistency, visual quality, AI-slop detection, and responsive behavior. Use when evaluating how a built UI looks and feels. For accessibility use /accessibility-audit; to build new components use /ui-component-builder.

• doc-gardening

  Cross-check docs/ against current code — flag stale file paths, broken cross-references, removed APIs, and outdated examples. Use when docs may have drifted after code changes. For doc completeness and quality use /documentation-audit instead.

• documentation-audit

  Audit documentation quality — inline comments, API docs, README completeness, and doc-code sync. Use when assessing whether docs are good and complete. To catch docs that have gone stale versus the code use /doc-gardening instead.

• feature-cycle

  End-to-end orchestrator chaining spec → plan → implement → verify → review → ship from a local spec — the whole CLAUDE.md lifecycle as one command. Use to drive a complete feature from a ready spec. To validate what to build first use /office-hours.

• harness-init

  Scaffold a docs/ harness (ARCHITECTURE, DESIGN, PLANS, QUALITY_SCORE, RELIABILITY plus design-docs/, exec-plans/, references/). Idempotent — never overwrites. Use once when adopting the harness pattern in a repo lacking docs/ structure.

• interface-design

  Design It Twice — spawn 3-4 parallel sub-agents producing radically different interfaces for a module, then compare on depth, locality, and seam placement. Use before committing to a new interface or public API.

• lesson-refresh

  Periodic maintenance of tasks/lessons/ — decide keep/update/promote/encode/archive per lesson by relevance, recency, and prior encoding. Use to prune lesson rot. To recall dormant lessons for the current task use /lesson-resurface instead.

• lesson-resurface

  Surface archived or superseded lessons whose topic tags match the current task — returns pointers (paths only), never bodies. Use when a task touches an area past sessions may have covered, to recover dormant context without bloating boot.

• mcp-audit

  Audit the project's configured MCP servers against the trust allowlist (.claude/mcp-allowlist.txt) that .claude/hooks/mcp-gate.sh enforces. Lists every configured server, flags the ones not allowlisted (blocked by the gate, or running untrusted while it is off), and surfaces prompt-injection and sup

• note

  Append a timestamped mid-session note to the session journal — finding/decision/summary tags for across-compaction memory. Use when you discover something the session must remember past /compact. Folded to the handoff at session end.

• office-hours

  Pre-coding product validation using forcing functions — clarify what to build and why before any code. Use at the start of a feature when scope or value is fuzzy. To turn a validated idea into a spec use /shape-spec; to run the build use /feature-cycle.

• performance-audit

  Identify performance bottlenecks — rendering, startup, memory, and I/O — across any stack. Use when the app is slow, before perf-sensitive releases, or when the user mentions latency, jank, or memory growth.

• project-health-report

  Comprehensive whole-project health report across code quality, architecture, testing, dependencies, and documentation. Use for a breadth-first snapshot of the entire repo. For PR-scope diffs use /review-pipeline; for one dimension use the specific /*-audit.

• pulse

  Time-windowed pulse report on what shipped, broke, was learned, and is open — saved to tasks/pulses/ as a timeline. Use to summarize a recent period of work. Distinct from /retro (process) and /project-health-report (whole-project code health).

• quality-audit

  Audit the codebase against the project's golden-principles.yaml — runs deterministic detection rules and updates docs/QUALITY_SCORE.md. Use to enforce project-specific principles. For a generic smell pass with no rules file use /code-quality-audit.

• refactoring-guide

  Fowler-based refactoring recommendations with specific techniques, risk assessment, and step-by-step plans. Use when code needs restructuring and you want a safe execution plan. To first locate structural issues use /architecture-review.

• references-sync

  Sync llms.txt-style dependency reference docs into docs/references/ so the agent has library docs in-context — scans package manifests and fetches known vendor references. Use when working with a third-party library whose docs aren't yet local.

• retro

  Weekly retrospective with session analytics, LOC metrics, pattern detection, and persistent history. Use to reflect on how work went over a week. For what shipped/broke as a timeline use /pulse; for raw session numbers use /scorecard.

• review-pipeline

  Run multiple audits in parallel over a PR-scope diff, dedupe across auditors, and produce a confidence-gated report. Use to review a change or PR before merge. Distinct from /project-health-report (whole-project, breadth-first).

• scorecard

  Aggregate recent session scorecards from reports/session-audit.log into per-session and windowed summaries — pure numbers, fed by the SessionEnd hook. Use to see quantitative session trends. For narrative reflection use /retro instead.

• shape-spec

  Create a timestamped feature-spec folder with structured plan, decisions, and references for multi-session features. Use to capture a spec before building something non-trivial. To validate the idea first use /office-hours; to execute it use /feature-cycle.

• ship

  Full deployment pipeline — tests, coverage audit, CHANGELOG generation, bisectable commits, and PR creation. Use when a change is verified and ready to ship as a pull request.

• skill-extractor

  Extract non-obvious knowledge discovered during a session into a reusable SKILL.md. Use right after learning something hard-won — a framework quirk, a verified fix. To generate skills proactively from stack analysis use /skill-generator instead.

• skill-generator

  Generate project-specific coding skills by analyzing tech stack, architecture, and constraints. Use when bootstrapping skills for a new project. To capture a single insight discovered mid-session use /skill-extractor instead.

• testing-audit

  Audit the test suite for coverage gaps, test quality, flaky tests, and strategy alignment. Use when assessing test health before a release, or when tests feel weak, slow, or flaky.

• ui-component-builder

  Build production-ready UI components with accessibility, loading/empty/error states, responsive behavior, and reusable props — not retrofitted polish. Use when creating a new component. To review an existing UI use /design-review instead.

• verification-status

  Render the per-task verification ledger (.hook-state/verification-ledger.json) — which gates ran and their outcomes — and record the manual checks CLAUDE.md mandates but a hook can't capture: the smoke-test result and silent-failure counts. Use before /ship or marking a task done, or when asked "did

• web-read

  Extract clean, readable markdown from a web page with the Defuddle CLI — strips nav, ads, and boilerplate to cut tokens versus WebFetch. Use when given a URL to read or analyze (docs, articles, blogs, changelogs, RFCs). Do NOT use for .md or JSON/API URLs — use WebFetch directly.

• wiki-briefing

  Morning briefing from the knowledge wiki — recent activity, new sources, open actions, and key updates

• wiki-ingest

  Ingest a new source into the knowledge wiki — read, summarize, cross-reference, and update index

• wiki-lint

  Health-check the knowledge wiki — find contradictions, orphans, missing pages, and stale content

Subagents (6)

• code-reviewer

  Thorough code reviewer focused on correctness, maintainability, and performance

• dead-code-remover

  Removes verified unused code through static reference analysis across the entire project

• devils-advocate

  Adversarial reviewer that tries to falsify a change rather than approve it — surfaces unstated assumptions, the input that breaks it, the requirement it quietly reinterprets, and "works on my machine" gaps. Returns a ranked falsification list, not a checklist pass.

• planner

  Implementation planner that analyzes tasks, explores the codebase, and produces actionable plans

• qa-reviewer

  Evidence-based QA reviewer that verifies task completion against contracts and verification criteria

• security-reviewer

  Security-focused code reviewer that finds vulnerabilities, not style issues

Hooks (28)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/session-start.sh

• UserPromptSubmit

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/prompt-router.sh

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/protect-files.sh

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/protect-changes.sh

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/glob-guidance.sh

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/branch-protect.sh

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/block-dangerous-commands.sh

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/conventional-commit.sh

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/commit-gate.sh

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/subagent-pre.sh

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/mcp-gate.sh

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/secret-scan.sh

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/unicode-scan.sh

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/loop-detect.sh

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/quality-gate.sh

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/test-first.sh

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/test-run.sh

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/bash-budget.sh

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/read-budget.sh

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/subagent-post.sh

• PostToolUseFailure

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/tool-failure-observe.sh

• Stop

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/stop-gate.sh

• Stop

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/test-first-gate.sh

• Stop

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/task-complete-notify.sh

• StopFailure

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/stop-failure-observe.sh

• SessionEnd

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/session-end.sh

• SessionEnd

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/journal-fold.sh

• SessionEnd

  "${CLAUDE_PLUGIN_ROOT}"/.claude/hooks/next-red-test.sh

Similar plugins