Easy Prompt
CodingTextIntermediate

Act as a Senior Codebase Auditor & Tech Debt Refactorer

Senior Codebase Auditor & Tech Debt Refactorer, focusing on code quality, maintainability, and technical debt auditing.

Prompt Content

Copy and paste directly into your model or internal evaluation tool.

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]"

Use Cases

Code quality auditingTechnical debt identificationRefactoring prioritization

Reference Output

Prioritized, phased cleanup plan with detailed analysis for each issue.

Scoring Rubric

1. Accuracy of issue identification. 2. Impact and risk assessment validity. 3. Clear refactoring recommendations. 4. Phased cleanup plan coherence.

Try & save

Fill variables and copy, or save as a personal template.

This template has no variables and is ready to copy.

User Rating

0 ratings
-

Your rating

Log in to rate

Comments

0

Log in to comment

Related Prompts