skill-collision-audit

Test-driven development, red then green, one vertical slice at a time. Use when building a feature, a rule, a config option or a bug fix test-first, when the user says "TDD", "red-green" or "write the test first", or when a subagent is handed a ticket to build.

Prove a change before claiming it is done - judge lint, typecheck, tests and git push by their exit codes rather than by reading output, and show that a bug fix's regression test fails without the fix. Use before saying "tests pass", "lint is clean", "pushed" or "fixed in <sha>"; before opening or updating a pull request; whenever a command is piped into grep, tail or head; and whenever a bug fix or false-positive fix ships with a new test. For whether a measured number (a score, a timing, an eval result) can be credited to a change, use `explain-the-number`.

Investigate a question against primary sources and capture the findings as one cited Markdown note. Use when the user wants a topic researched, a vendor's docs or API facts gathered, a library's or tool's real behavior confirmed, or reading legwork delegated while the main session keeps working.

Review a finished coding session for what slowed the agent down or let a mistake through, and turn one lesson into a test, check or doc in the project so the next session does not repeat it. Use when the user asks for a retro or retrospective, a post-mortem of a session, or "what should we change so this doesn't happen again". To carry unfinished work into a new session, use `handoff`; to prove a fix before claiming it, use `regression-proof`.

Runs Cloudflare's security-audit skill in full audit mode from Claude Code. It builds each agent's prompt file from that skill's text, pulls each agent's JSON reply out of its transcript, and keeps the coverage ledger, findings, agent-call budget and NEEDS-VALIDATION.md. Use it together with `security-audit` when the user asks for a full, end-to-end or report-producing security audit or pen test of a codebase. For a security question or a focused review, use `security-audit` alone.

Route a multi-step task across cheaper subagents while the main session keeps the plan, the judgment calls and the verification. Use at the start of any task with more than one step, before spawning a subagent, when picking a model for a subtask, when a subagent fails, or when the user mentions cost, tokens or model choice.

Shorten an existing ticket that is too long or too technical, moving the engineering detail into a Technical notes comment so nothing is lost. Use when the user gives a ticket key or link and asks to trim, condense, simplify or clean it up, or says a product owner or analyst found it hard to read.

Writing documents for agents. Use when creating or editing a skill (its SKILL.md, description or reference files), when modifying AGENTS.md or CLAUDE.md, or when reviewing an agent-facing document that behaves inconsistently across runs. Prose that people read, such as a memo or a one-pager, follows its own rules.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Teach the user a new skill or concept, within this workspace.

No description in the SKILL.md.

No description in the SKILL.md.

Ask which skill or flow fits your situation. A router over the skills in this repo.

No description in the SKILL.md.

Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.