19,479 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
Run the full pre-PR review per AGENTS.md §7 — gates, tagged diff walk, pessimistic meta-check, acceptance-criteria mapping, commit hygiene, rebase status, PR-description draft. Use when the human says "ship it", "ready to PR", "open the PR", "pre-PR check", or invokes /pre-pr.
Trace the impact (blast radius) of a code change in ANY codebase and prove it didn't break anything else — language- and framework-agnostic. Use RIGHT AFTER a fix to a feature, function, module, type, route, API endpoint, schema, or config, before committing, opening a PR, or pushing. Triggers: "did this break…
Use for plan reviews and checkpoint reviews during implementation. Pass -Tier to select model preference: high-risk uses Opus 4.6 first, medium uses Sonnet 4.6 first. Supports relaxed cadence after 2 consecutive clean reviews.
Reimplement a messy git branch with clean, narrative-quality commit history suitable for code review. Use when a branch has WIP commits, debug commits, or trial-and-error history that needs to be transformed into a reviewable story before creating a PR.
Orchestrate a Coder→Quality iteration loop against a story's Verification contract. Use when a story has a complete Verification section and is ready for execution with automated review.
Expert code reviewer specializing in code quality, security vulnerabilities, and best practices across multiple languages. Masters static analysis, design patterns, and performance optimization with focus on maintainability and technical debt reduction.
Self-review gate and outcome decision checklist for BitGN PAC tasks. Use IMMEDIATELY before calling bitgn answer to verify correctness, security, outcome code, and refs completeness.
Parallel Codex code reviews for Claude Code. N independent agents (diff, security, tests, architecture) review your changes with project-aware context. Includes self-review, anti-pattern detection, and knowledge compounding.
★not rated 2 3mo agoA
tokens not measured
originalMIT
Review an existing code change, patch, pull request, commit, or working tree diff for defects, regressions, security issues, data risks, and important missing tests. Use when the primary task is evaluating code that already exists. Do not use for implementing an ordinary feature from scratch.
Top-down, whole-system audit of a codebase's DEEP LOGIC - the bugs that live in the SEAMS between modules, not inside any one file. Finds contracts that drift across module boundaries, invariants enforced on one path but broken on a sibling path, cross-cutting responsibilities (deletion cascade, tenant-scope…
Run the full review panel — test-specialist, security-auditor, code-reviewer, code-simplifier, and architecture-reviewer — in parallel against the current uncommitted working tree, then return one consolidated verdict.
Quality review of the full Plan→Build→Verify chain for the Reviewer role. Use when the Reviewer needs to assess whether the implementation matches the Planner's design intent — checking code quality, architecture compliance, verification completeness, and producing a review report with a pass/revise decision, with…
Revisa uma única PR do GitHub e posta os comentários inline. Projetado para ser disparado em paralelo — um subagente por PR. Requer no brief: número da PR e owner/repo.
Runs the vibe-check static analyzer on Claude skills, agents, and CLAUDE.md files, then fixes the findings and trims token cost. Use when the user wants to lint, score, review, fix, or improve a skill or agent file, asks why a skill scores badly, or wants to audit skills they installed.
Reviews code changes for quality, security, and correctness. Use when the user says "review this", "check my PR", "look over these changes", "is this safe", or "what do you think of this code". Covers: logic errors, security issues, style violations, missing tests, and architectural concerns.
Review code quality with all 18 dimensions. Analyzes diff, gathers deep context, checks Known Gotchas, presents findings grouped by severity. If a PR exists, posts inline comments on GitHub. Use when the user says "code review", "review this PR", "review PR", "review", "pre-review", "check quality", or before opening…
Compound engineering: every session leaves your setup smarter. Verify, learn, audit, refactor -- with hooks, rules, and skills that prevent discipline decay.
★not rated 2 7mo agoA
tokens not measured
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: