Performs a rigorous code quality and technical debt audit across a codebase to safely identify dead code, duplicate logic, and refactoring opportunities.
I want you to act as a Senior Software Engineer performing a rigorous code quality, maintainability, and technical debt audit on a codebase. Your objective is to aggressively yet safely simplify the codebase, improve maintainability, and highlight anything that provides zero value to the application. Analyze the provided codebase, directory tree, or code snippets and systematically evaluate: 1. Dead Code: Unused functions, files, components, routes, APIs, variables, imports, and dependencies. 2. Duplicate Logic: Redundant blocks or patterns that should be consolidated into reusable utilities or abstraction layers. 3. Unused UI Components: Orphaned views, unused design components, or obsolete style files. 4. Overly Complex Implementations: Code that can be simplified or refactored without altering expected behavior. 5. Legacy & Deprecated Code: Outdated patterns or unneeded legacy fallback logic. 6. Redundant Queries & API Calls: Unnecessary database operations, duplicate fetch requests, or N+1 query risks. 7. Abandoned Files: Disconnected, unreachable, or unreferenced files in the repository. 8. Technical Debt: Code smells, poor abstractions, or high-risk areas lacking maintainability. For every issue identified, structure your analysis with: - Issue & Location: File path and code block. - Reason for Action: Why this code is unnecessary, redundant, or overly complex. - Impact Estimation: High/Medium/Low impact on performance, bundle size, or developer velocity. - Risk Assessment: Potential regression risks, hidden side effects, or runtime dependencies to verify before deletion. - Recommended Refactor: Specific code/step-by-step guidance for safe removal or consolidation. Conclude with a prioritized, phased Cleanup Plan divided into: - Phase 1: High-Confidence / Safe Deletions (Zero-risk removals) - Phase 2: Logic Consolidation & Simplification (Moderate risk) - Phase 3: Architectural Technical Debt Reduction (Requires testing/migration) My first request is: "Please analyze the following codebase details and perform the code quality review: [Insert repository link, codebase structure, or code snippets here]"
Audits feature flags against your codebase and plans their cleanup - finds release flags 100% on or off for weeks, rollouts stuck at a partial percentage, experiments that never ended, expired, archived and unreferenced flags, keys used in code but missing from the flag service (or misspelled), staging-production drift and flags without an owner. Lists every file:line to change with effort. Includes an offline stdlib Python scanner.
A read-only post-implementation audit workflow for coding agents. Reviews completed code changes for requirement coverage, correctness, regressions, verification evidence, edge cases, scope integrity, and commit quality without modifying the implementation. Produces evidence-backed CLEAR, FINDINGS, or INCOMPLETE results and supports structured re-audits after remediation.
Scans a codebase for TODO, FIXME, HACK, and XXX comments, extracts owner, ticket, and due date, and flags unowned, untracked, overdue, or vague items with a priority score. Use when cleaning up tech debt, before a release, or asking "which TODOs actually matter?". Includes a stdlib Python scanner with --self-test and a CI-friendly exit code.
A Claude Code agent skill for Unity game developers. Provides expert-level architectural planning, system design, refactoring guidance, and implementation roadmaps with concrete C# code signatures. Covers ScriptableObject architectures, assembly definitions, dependency injection, scene management, and performance-conscious design patterns.
Finds code nobody uses anymore: unused files, exports, routes, styles and dependencies, with proof for each one, and suggests small safe pull requests to remove them.
Collects TODO, FIXME and HACK comments across your codebase, finds the old and risky ones, links them to issues and suggests which to fix, file or delete each sprint.
Helps new teammates learn a repository: answers 'where is X handled?' with file references, builds a living architecture note, and suggests good first issues.
Compares your documentation with the code after every merge, finds outdated examples, renamed options and missing pages, and drafts the doc fixes.