Make any repo AI-first - write sustainable code from the start, or refactor a legacy codebase to prepare it for agent-driven development.Building blocks for Claude Code: subagents, slash commands, hooks, and workflow patterns. Copy what you need. A working developer's stack for Claude Code.
USE WHEN a test intermittently fails on unchanged code. Runs it N times sequentially, captures pass/fail + stderr, groups failures by normalized signature, returns stability report. Read-only — never modifies code or installs deps. For statistical signal across runs, not one-shot diagnosis.
USE BEFORE committing security-sensitive changes (auth, crypto, routes, templates, secrets). Audits current diff for OWASP-Top-10 patterns + deps typosquatting. Read-only. Returns Critical / Important / Nice schema with file:line. Model review — not a Semgrep/CodeQL replacement.
Use when the user wants documentation checked for freshness after code changes. Reads diff and existing docs, proposes specific updates to README, CHANGELOG, docstrings, and other documentation files. Read-only - returns prose-direction suggestions, never modifies files.
Review pre-extracted code snippets passed in the prompt — never re-reads files, never runs git diff. Hard 500-token output cap. Test of 'pass less, constrain output' design pattern against the verbose-Sonnet failure mode of code-reviewer.
Find all call sites of a symbol with structured output on Haiku — for 'what breaks if I change X?' questions. Returns file:line:snippet triples plus tests + external risk. Bounded to prevent Opus from reading every hit inline.
Run a shell command and return structured digest of its output on Haiku — for commands that produce >2k tokens of output (pip install, docker build, npm audit, large test runs, etc.). Saves Opus from reading verbose logs.
Use for codebase discovery. Use to find where something is defined or imported. Use to identify patterns used across files. Use proactively before making changes that might affect multiple files. Read-only - returns structured findings report. Does not propose changes, suggest refactoring, or write code.
Use to understand how something works in the codebase before making changes. Use when asked to explain a pattern or flow that spans multiple files. Use proactively when planning non-trivial changes that depend on existing patterns. Read-only - returns structured synthesis. Does not propose changes, suggest…
Run tests on Sonnet — auto-detects framework, returns structured failure analysis, read-only.
★not rated 68 1mo agoA24 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: