riding-codebase

Analyze codebases to generate documentation artifacts and detect drift.

5|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/0xHoneyJar/loa-beauvoir --skill riding-codebase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: riding-codebase
Source: https://github.com/0xHoneyJar/loa-beauvoir/tree/main/.claude/skills/riding-codebase
Command: npx skills add https://github.com/0xHoneyJar/loa-beauvoir --skill riding-codebase

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of understanding and documenting existing codebases, bridging the gap between code reality and human understanding.

Core Features & Use Cases

  • Codebase Analysis: Deeply inspects code structure, identifies entry points, data models, and dependencies.
  • Drift Detection: Compares code reality against legacy documentation and user context to flag inconsistencies.
  • Artifact Generation: Produces evidence-grounded artifacts like PRDs, SDDs, and governance reports.
  • Use Case: Onboarding a new developer to a complex legacy system by providing them with an up-to-date, evidence-based understanding of the codebase's current state and documentation accuracy.

Quick Start

Use the riding-codebase skill to analyze the current repository and generate a drift report.

Frequently Asked Questions about riding-codebase

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

FAQPage Schema
How do I detect drift between legacy documentation and my actual codebase?

To detect drift in your codebase, the skill validates actual code structure against legacy documentation and user-provided context, flagging inconsistencies to ensure code reality aligns with perceived state.

What is the best way to generate documentation artifacts for a legacy system?

Generating documentation artifacts for legacy systems is achieved by analyzing the codebase to extract factual representations, producing evidence-grounded PRDs, SDDs, and governance reports.

How do I audit API routes and data models in an existing codebase?

You can audit API routes and data models by deeply inspecting the codebase structure, identifying entry points, dependencies, and technical debt markers to generate a comprehensive factual report.

Can I use this for onboarding developers to complex legacy systems?

Yes, you can use this for onboarding developers to complex legacy systems by providing an up-to-date, evidence-based understanding of the codebase's current state and documentation accuracy.

Does codebase analysis work for identifying environmental dependencies and technical debt?

Codebase analysis works for identifying environmental dependencies and technical debt markers by deeply inspecting code structure and validating it against existing documentation to report factual alignment.