Use when implementing, debugging, refactoring, or reviewing code — enforces the think → analyze → verify → execute workflow — even when the user just says 'implement X' without…
Compares two tables or query results and diagnoses exactly how they differ — row counts, key set differences, per-column value mismatches — for migration and refactor validation.
Audit Python classes and OOP code for structural anti-patterns, naming inconsistencies, and data modeling issues.
Use when user describes a business requirement spanning 2+ domains. TRIGGER when: requirement involves 2+ domain keywords defined in project CLAUDE.md routing table, user asks…
Execute TDD implementation from task list following RED-GREEN-REFACTOR cycle with mandatory tests, stub detection, and quality gates.
Identify, quantify, and prioritize technical debt in the codebase. Activate when user mentions "tech debt", "code quality", "technical debt", "code smells", "refactor candidates",…
Use whenever a rewrite, redesign, or refactor would remove, replace, or overwrite copy or visuals that are already in place — a tuned headline, a converting landing page, a hero,…
Conventions for writing or editing bash CLI scripts in ~/dotfiles/bin/ — argument parsing, validation, error format, file structure.
Use a repo-root `.editorconfig` to configure free .NET analyzer and style rules. Use when a .NET repo needs rule severity, code-style options, section layout, or analyzer…
Review .NET changes for bugs, regressions, architectural drift, missing tests, incorrect async or disposal behavior, and platform-specific pitfalls before you approve or merge…
Use free built-in .NET maintainability analyzers and code metrics configuration to find overly complex methods and coupled code.
Use the open-source free `QuickDup` clone detector for .NET repositories. Use when a repo needs duplicate C# code discovery, structural clone detection, DRY refactoring…
Use when reviewing PRs/diffs/branches/documents for .NET quality, correctness, performance, security, data access, messaging, and observability.
Use when you need CRAP score and coverage risk analysis to find high-risk code before refactoring or release.
Don't Repeat Yourself (DRY) and Never Reinvent the Wheel (NRtW) - core b00t principles. Use existing libraries, leverage Rust via PyO3 instead of duplicating logic in Python, and…
Use when user asks to "remove duplicates", "DRY up code", "extract common logic", "consolidate repeated code", or when /dry scan finds duplicates.
Guides systematic code refactoring following the DRY (Don't Repeat Yourself) principle. Use when user asks to eliminate code duplication, refactor repetitive code, apply DRY…
Orchestrate a parallel multi-agent build with mandatory cross-review across Claude and Codex. Splits a multi-component coding task into ~equal Claude and Codex subtasks, runs them…
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and — from…
Third-party Claude Code token/context/code-review tools. Use when choosing or recommending an external tool to reduce token usage, manage context, or review large codebases…
Use when analyzing the Reactive Agents codebase for architectural improvements, abstraction opportunities, composability gaps, or Effect-TS engineering quality — before proposing…
Use when explaining, debugging, refactoring, or teaching Effect-TS and functional TypeScript.
Analyzes and refactors Go code using Effective Go principles. Use when refactoring Go code, identifying anti-patterns, improving Go idioms, or applying Go best practices.
Use BEFORE generating, refactoring, reviewing, or debugging code. Trigger phrases include "write a function/script/class for X", "review this code/diff/PR", "refactor this",…
Index a codebase's structure (folders, files, symbols) into Browzer's workspace graph via `browzer init` + `browzer workspace index`.
Audible code-quality reactions for code reading, review, refactoring, debugging, and repository exploration.
Use when the user asks to create a CodeTour .tour file — persona-targeted, step-by-step walkthroughs that link to real files and line numbers.
How to approach a coding task like a senior engineer — classify it (fix / refactor / feature / review / explore / migrate), map blast radius before editing, and self-review both…
Applies Chesterton's Fence, Occam's Razor, the Peter Principle, and Dunning-Kruger to technical decisions.
Identify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks abo — from…
Use when modernizing legacy Entity Framework data layers to EF Core with help for model mapping, DbContext refactors, phased cutovers, and migration risk review.
Apply the Explore → Plan → Code → Commit workflow for tasks like implementing features, fixing bugs, refactors, or adding integrations.
ERNE — Comprehensive code review combining code quality and performance analysis
ERNE — Create native modules with sequential native-bridge-builder then code-reviewer agents
Wartungsprobleme nach Schweregrad triagieren, Befunde mit Kontext dokumentieren, an geeigneten Spezialisten-Agenten oder Menschen weiterleiten und umsetzbare Fehlerberichte…
Bug-fix discipline — every defect has an etiology, the chain of cause that produced the observable fault; trace it before patching.
Specialized code quality evaluator for the Evaluate-Loop. Use this for evaluating code implementation tracks where the deliverable is functional code — features, API routes, state…
Search, analyze, and refactor Elixir code with `ex_ast` AST patterns in projects that already depend on `ex_ast`.
AI-powered code review tool that analyzes code for bugs, style issues, and improvements
What - AI エージェントがタスク実行依頼（バグ修正・パフォーマンス改善・リファクタリング・新機能開発等）を 受けた際に、7 ステップの標準ワークフローに沿ってタスクを遂行する。 各ステップの詳細手順は `docs/agent-tasks/agent-workflow/` 配下の step 別ドキュメントに Progressive…
Use Gortex to index one or more repositories into a local code graph and expose symbol, call-chain, blast-radius, review, and refactoring tools through MCP, CLI, API, or web UI.
Enforces confirmation workflow for EXTERNAL system writes (Jira, Confluence, BitBucket, Slack) ONLY. NEVER activates for Linear operations (Linear is internal tracking).
Model-only refactoring playbook for pulling a coherent block out of a long function into a named helper.
Model-only refactoring playbook for splitting a multi-concern file into layered modules.
Reviews ExUnit test code for proper patterns, boundary mocking with Mox, and test adapter usage. Use when reviewing _test.exs files or test helper configurations.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements — from engineering/code-quality
Autonomous large codebase migration agent optimised for Claude Fable 5 (Mythos class). Scopes the migration, builds a dependency-ordered wave plan, executes incremental file…
Use when you need a deep, honest audit of a repository with a prioritized improvement plan — before a refactor, before onboarding a new contributor, or before committing to a…
Apply factory function patterns to compose clients and services with proper separation of concerns. Use when creating functions that depend on external clients, wrapping resources…
Code quality specialist: architecture patterns, refactoring, code review, development practices. 23 methodologies.
Strategia di migrazione da codebase legacy. Analisi, piano incrementale, strangler fig. Trigger: "migrazione", "legacy", "refactor completo", "modernizzare"
Practical guidance for writing, refactoring, and reviewing fast, reliable, and maintainable Rust code.
Reviews Rust FFI code for type safety, memory layout compatibility, string handling, callback patterns, and unsafe boundary correctness.
Review code changes for FFP project standards including multi-tenant security, British English, architecture patterns, and SOLID principles.
Write Python code following FiftyOne's official conventions. Use when contributing to FiftyOne, developing plugins, or writing code that integrates with FiftyOne's codebase.
Map file structure and organization for downstream review and refactoring workflows
Organize project files and folders for maintainability and scalability. Use when structuring new projects, refactoring folder structure, or establishing conventions.
File a new tech-debt GitHub issue for an out-of-scope code-review finding, building the dedup key, checking for an existing open or declined-closed match, and only if none exists,…
Use when the user references a SPECIFIC FILE in a coding task — "fix the bug in routes/cost.py", "what was that change to api.ts about", "refactor…
Use when recording, tallying, or triaging stochastic review findings — the append-only JSONL ledger where Tier 2 (advisory, unevidenced) reviewer output goes instead of blocking…