Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…
Performs a thorough hardware design review of a KiCAD project. Triggers: full design review, audit everything, is my board ready for fab, comprehensive check, pre-fab review.
Adversarial pre-merge review of a pi-lens PR. Use for every PR before merge, including small and self-authored ones. Spawn with the PR number, a one-paragraph summary of what the fix claims, and any PR-specific attack angles; this playbook supplies the rest.
Use this agent when you want a comprehensive review of code quality, readability, structure, and maintainability. This agent focuses on how well-written and organized code is — not on bugs, logic errors, or functional correctness. It examines file length, function complexity, naming conventions, code organization…
Use this agent when you need a thorough code quality analysis and refactoring recommendations for specific files, directories, or an entire branch. This agent reads code deeply, questions every pattern, checks for modern best practices, and produces a detailed report — without making any changes.\n\nExamples:\n\n…
Use this agent when you need a thorough review of TypeScript type definitions, type usage patterns, and type architecture in recently written or modified code. This includes checking for type duplicates, unnecessary custom type copies that should be imported from libraries, improper type assertions, overly broad…
Use this agent when you need to analyze and refactor code structure, identify architectural issues, or improve code organization. Examples: Context: User has just implemented a new authentication feature and wants to ensure it follows project architecture patterns. user: 'I just finished implementing the login flow…
Use this agent when you need to perform comprehensive security audits of your codebase, particularly focusing on credential management, token handling, and client-server architecture security. Examples: Context: User has just implemented OAuth authentication in their mobile app and wants to ensure secrets are properly…
Convention compliance reviewer grounded in ApkAnalyzer's AGENTS.md files and docs/engineering/ conventions. Cites the exact rule it's enforcing. Never invents conventions.
Use when reviewing React+TypeScript code for compliance with frontend standards. Reviews modified files from git diff or a specific file/folder. Reports violations with file:line references and suggests fixes. Invoke as: @frontend-reviewer (reviews git diff) or @frontend-reviewer (reviews specific path).
Use this agent when you need to verify that your project's dependencies are being used according to their official recommendations and best practices. This includes checking for deprecated patterns, security vulnerabilities, outdated usage patterns, and ensuring alignment with the latest documentation from each…
Main thread configuration for evidence-based code review sessions. Focuses on systematic review with evidence gathering and structured findings. Use via: claude --agent code-review-mode Or set in .claude/settings.json: { "agent": "code-review-mode" }.
MuninnDB's resident code reviewer. Use before opening a PR and when reviewing one. Reviews a change for correctness and for adherence to MuninnDB's cognitive, storage, and security invariants and its cross-surface sync obligations. Builds and tests the actual change (with -race where it matters) and RED-sanity-checks…
Builds a designed MuninnDB increment RED-first in an isolated worktree, then pushes the branch WITHOUT opening a PR so the adversarial review runs first. Use for the build pass of the increment loop ("build the design in X", "implement #N per the design"). Every behavior change lands with a test proven to fail without…
Use this agent when a major project step has been completed and needs to be reviewed against the original plan and coding standards. Examples: Context: The user is creating a code-review agent that should be called after a logical chunk of code is written. user: "I've finished implementing the user authentication…
Makes UI/UX, copy, and visual consistency decisions for 2anki.net. Use for new screens, flow changes, microcopy, error states, empty states, onboarding, or any visual review. Takes a problem and returns a concrete design recommendation, not options.
★not rated 324 yesterdayA56 tokens
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: