codebase-review

Review codebases for architecture drift, dead code, and testing gaps.

2|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/LightForgeLabsStudio/AIDE --skill codebase-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-review
Source: https://github.com/LightForgeLabsStudio/AIDE/tree/main/skills/codebase-review
Command: npx skills add https://github.com/LightForgeLabsStudio/AIDE --skill codebase-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining codebase health by proactively identifying architectural inconsistencies, unused code, and documentation or testing deficiencies without requiring manual code fixes.

Core Features & Use Cases

  • Architecture Drift Detection: Identifies deviations from established architectural patterns.
  • Dead Code Identification: Pinpoints unused code and assets that can be safely removed.
  • Test and Documentation Gap Analysis: Highlights areas lacking adequate test coverage or documentation.
  • Follow-up Issue Generation: Automatically creates GitHub issues for critical findings.
  • Use Case: A team can use this Skill to perform a quarterly review of their main branch to ensure adherence to coding standards and identify technical debt before it becomes a major issue.

Quick Start

Perform a codebase review of the main branch, focusing on identifying dead code and documentation gaps.

Frequently Asked Questions about codebase-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify dead code and architecture drift in my codebase?

A codebase review strategically samples project files to detect dead code and architecture drift, reporting findings by severity with file paths and impact. It analyzes project constraints to proactively identify technical debt without manual code fixes.

What is the best way to perform a codebase health check for technical debt?

A holistic codebase health check evaluates testing and documentation gaps by analyzing GitHub activity and project constraints. It samples code strategically to report technical debt findings by severity, creating GitHub issues for critical items.

How do I automatically create GitHub issues for code review findings?

You can generate GitHub issues for critical findings by running a strategic codebase review. The review identifies architecture drift, dead code, and documentation gaps, automatically creating issues to track necessary fixes.

Does the codebase review process require write access to modify code?

No, the codebase review process is strictly read-only. It analyzes project constraints and GitHub activity to identify technical debt, reporting findings by severity without modifying source code.

Can I use a code review tool to find testing and documentation gaps?

Yes, a codebase review identifies testing and documentation gaps by analyzing project constraints and sampling code. It reports these deficiencies by severity with file paths and impact to highlight areas lacking coverage.

When should I run a codebase health check to manage technical debt?

You should run a codebase health check quarterly on your main branch to identify architectural inconsistencies, dead code, and testing gaps. This proactive review ensures adherence to coding standards before technical debt escalates.