Total 52,261 skills, Code Quality has 2360 skills
Showing 12 of 2360 skills
Internal guidance for presenting Codex helper output back to the user
Use when onboarding to an existing codebase that lacks specifications — exhaustively traces code paths and produces implementation-free behavioral specifications for safe refactoring, feature addition, or legacy modernization
Start a code review session by launching the diffx server and opening the browser UI. Use when the user invokes /diffx-start-review.
Run full project validation (typecheck + lint + format + test + build (optional))
Automated code review and analysis. Use when: user wants to review code changes, check for issues, analyze complexity, or perform security scans.
Stabilize workflows with Template Method or Strategy; extend by adding new classes instead of editing core logic
Read-only drift detector. Diffs SPEC.md against current code and reports violations grouped by severity. Writes nothing — suggests remedies via the spec or build skills but never invokes them. Triggers when the user asks to check drift, audit the spec, verify invariants, or ask whether code still matches the spec. Phrasings: "check drift", "audit the spec", "does the code still match §V", "check invariants", "spec vs code".
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
Helps fail fast on risky implementation steps by prototyping before committing to full code changes. Use during planning or implementation when a step is ambiguous, depends on multiple subsystems or flaky tools, may invalidate the current plan, or when repeated fix attempts suggest a doom loop. Useful both at planning step and during implementation.
Review a PR or branch diff using the knowledge graph for full structural context. Outputs a structured review with blast-radius analysis.
Refactor code to simplify it without changing behavior.
Enforce C++ coding standards including camelCase or snake_case variables, PascalCase classes, and consistent file naming.