Menu
Use when editing or revising a skill (SKILL.md), prompt, rule, system message, or instruction to trim bloat.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when reviewing an implementation plan, codebase, feature area, or pull request for likely defects, missed requirements, weak tests, security gaps, data risks, UX mismatches, or reliability issues before or after implementation.
Use when writing, reviewing, or refining Gherkin, BDD scenarios, acceptance criteria, feature files, behavior specs, examples, user journeys, business rules, edge cases, or Given/When/Then wording.
Use when writing, reviewing, editing, or renaming tests, variables, functions, classes, types, components, scenarios, tickets, branches, or other identifiers where names may be vague, implementation-focused, misleading, or hard to understand.
Use when reviewing the active or named branch against a target branch, drafting GitHub review comments, verifying findings locally, or coordinating focused reviewer subagents.
Use for software development feature or bugfix work that should follow a strict red, green, refactor loop with isolated subagents, verified failing tests, minimal implementation, review gates, commits, pull requests, and ticket observations.
Use when validating that an Epic, Feature, parent ticket, or ticket subtree is coherent, dependency-safe, testable, and ready before implementation or TDD orchestration.
| name | keep-or-cut |
| description | Use when editing or revising a skill (SKILL.md), prompt, rule, system message, or instruction to trim bloat. |
Go through these instructions statement by statement. for each statement, tell me if we delete it; would the output get worse? we want to list these by file with the reasoning
