Final metric-driven refactoring pass. Runs ONCE after the last green cycle, over the whole production src/. Uses deterministic measurements (ESLint smells, SonarJS cognitive complexity, McCabe cyclomatic complexity) plus APP mass to drive improvements while keeping all tests green. Iterates one change at a time until…
A review process that checks whether a front end and back end agree on how an API works, including request fields, response data, types, and error codes.
Use this agent when you need to perform a comprehensive codebase audit to detect technical debt, outdated patterns, and architectural inconsistencies. Specific scenarios include:\n\n \nContext: After merging a large feature branch (feat/jar-xxx) into dev, the user wants to ensure code quality before creating a release…
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
An automated code-review guide for examining pull requests and code quality. A pull request is a proposed code change that others review before it is merged.
Audits cchb Rust source code for subprocess execution, path handling, JSONL parsing, sensitive-data leakage, and Rust safety/panic issues. Returns structured JSON findings. Read-only — no edits, no shell execution beyond grep/find/read. Used by the checking-cchb-security skill in parallel with…
Review Kubernetes operator code for convention violations. Use after modifying files under components/ambient-control-plane/. Checks for OwnerReferences, SecurityContext, reconciliation patterns, resource limits, and panic usage.
God-mode engineering meta-auditor. Scans .claude/ + docs/ + workspace/src/, outputs structured observation reports to docs/retrospectives/. Observes and suggests only — does not modify any .claude/ or docs/ files (except its own reports). Triggered by /meta-audit command, or spawned by main agent after major…
Reviews any front-end change (routes, src/ui components, styling, tokens) against statuslin.es's design system and React conventions. Use whenever a change touches src/routes, src/ui, src/styles, or adds/edits UI components.
Use this agent when you need comprehensive manual quality review, integration testing, and user experience validation. USE PROACTIVELY for quality gates - automated tools (lint/typecheck) are handled by hooks, this agent focuses on manual QA that requires human-level assessment. Examples: Context: User has just…
Full-repository technical audit agent. Use when the user asks for a codebase audit, health check, tech-debt review, or a prioritized improvement plan. Produces a Repo Map, severity-rated Audit Report, Improvement Strategy, and milestone-based Task Plan. Read-only — never modifies code.
Use when a major project step completes and needs review against the original plan and coding standards. Examples: Context: User finished implementing user authentication as step 3 of plan. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Let me use the…
Reviews changed code for correctness, security, and convention compliance before downstream delivery.
★not rated 10 2d agoA15 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: