Guides designing, reviewing, and refactoring modules for depth — maximizing functionality hidden behind minimal interfaces.
Revue de code structurée avec détection de bugs, suggestions d'amélioration et bonnes pratiques. À utiliser quand l'utilisateur colle du code et demande un avis, une revue ou des…
Use proactively before writing any code, fixing bugs, designing features, refactoring, or making any code changes in nekonote. Must be invoked before implementation begins.
Delegate code tasks to OpenAI Codex CLI using markdown file handoff pattern. Write instructions to TASK.md, Codex reads and executes, outputs to OUTPUT.md.
Pre-wrap quality gate. Runs /simplify on the working-tree diff, re-runs commands.test, and reports results. Suggests /code-review:code-review when installed.
Analyzes codebase against standards and generates refactoring tasks for ring:dev-cycle.
AUTO-ACTIVATE when working in flow-state-refactor worktree or refactoring large components. MANDATORY port 5550 for refactor worktree.
AUTO-ACTIVATE when working in flow-state-refactor worktree or refactoring large components. MANDATORY port 5550 for refactor worktree.
Review and audit code quality, architecture, and implementation. Verify code meets design specs, find bugs, identify improvements, and create change/bug/improve backlogs.
Developer tools for The Fold - protocols (extensible dispatch), protocol bundles, refactoring toolkit (rename, move, dead code), and template DSL.
General principles for exploring, developing, editing, and refactoring code. Use for codebase analysis, implementation tasks, and code quality improvements.
Use when implementing, debugging, refactoring, or reviewing code — enforces the think → analyze → verify → execute workflow — even when the user just says 'implement X' without…
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 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…
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…
Use when analyzing the Reactive Agents codebase for architectural improvements, abstraction opportunities, composability gaps, or Effect-TS engineering quality — before proposing…
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",…
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.
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…
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…
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…
AI-powered code review tool that analyzes code for bugs, style issues, and improvements
Enforces confirmation workflow for EXTERNAL system writes (Jira, Confluence, BitBucket, Slack) ONLY. NEVER activates for Linear operations (Linear is internal tracking).
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
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"
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.
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…
Safe refactoring superbrain — code smell detection, TypeScript migration, dead code removal, pre/post verification
Use when reviewing or authoring Flow logic that contains a Loop element — covers DML-in-loop / SOQL-in-loop refactors, the collect-then-DML idiom, nested loops, and loop-free…
Use when planning refactoring sprints, prioritizing technical debt backlog, justifying refactoring investment to executives, or creating data-driven roadmaps - calculates return…
Reviewing pull requests well. What to look at first, what to skip, severity prefixes, when to block vs approve, frame feedback as questions, never rewrite-as-review, reviewing…
Microsoft Foundry agent deployment, orchestration, and cloud-native AI service patterns
Expert usage of Foundry (Forge, Cast, Anvil, Chisel) for smart contract development, testing, and deployment.
Build agentic retrieval solutions with Azure AI Search knowledge bases and Foundry Agent Service using the Python SDK.
Build and test Solidity smart contracts with Foundry toolkit. Use when developing Ethereum contracts, writing Forge tests, deploying with scripts, or debugging with Cast/Anvil.
Comprehensive guide for refactoring imperative TypeScript code to fp-ts functional patterns
Apply SOLID, DRY, KISS, YAGNI, and SSOT principles when writing, reviewing, or refactoring code to ensure maintainability and quality.