Codebase Analyzer Skill

Analyze codebases to reverse-engineer requirements, design, and implementation status.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/larus-peritus/pel_web --skill codebase-analyzer-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Codebase Analyzer Skill
Source: https://github.com/larus-peritus/pel_web/tree/main/.claude/skills/codebase-analyzer-skill
Command: npx skills add https://github.com/larus-peritus/pel_web --skill codebase-analyzer-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams understand and document existing codebases by reverse-engineering requirements, design, and implementation status from the code itself.

Core Features & Use Cases

  • Automatic discovery of features, architecture, and gaps from apps/[app-name]/
  • Generation of formal specs (requirements, design, and tasks) that align with observed implementation
  • Baseline documentation updates: Create or update context and design docs to guide refactoring and onboarding.

Quick Start

Analyze the codebase located at apps/your-app/ to generate specifications covering requirements, design, and implementation status.

Frequently Asked Questions about Codebase Analyzer Skill

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

FAQPage Schema
How do I reverse-engineer requirements and design from an existing codebase?

To reverse-engineer requirements from a codebase, you analyze source, tests, and configs to extract identified features and architecture patterns, producing structured specs that align with the observed implementation.

What is the best way to generate architecture notes and documentation for legacy code?

Generating architecture notes for legacy code involves scanning entire application directories to discover implementation gaps and features, which outputs formal specifications and baseline context docs to guide refactoring and onboarding.

Can I analyze test and config files alongside source code to produce structured specs?

Yes, you can analyze test and config files alongside source code, because the analysis scope explicitly includes entire app directories to produce comprehensive requirements, design specifications, and a prioritized task list.

How to create a prioritized task list for refactoring a messy codebase?

You create a prioritized refactoring task list by reverse-engineering the implementation status of your application directory, identifying architectural gaps, and outputting structured tasks designed to guide subsequent code improvements.

Does this codebase analyzer work with monorepo structures like apps/app-name/?

Yes, this codebase analyzer specifically scopes its reverse-engineering process to entire application directories located under apps/[app-name]/, successfully mapping their source, tests, and configurations into formal design specs.