ride

Analyze codebases to extract API routes, data models, and dependencies into Loa artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Ride skill analyzes an existing codebase to generate evidence-grounded Loa artifacts, turning code reality into the grimoire.

Core Features & Use Cases

  • Evidence-grounded code reality extraction: identify API routes, data models, environment dependencies, and potential dead code.
  • Drift analysis against docs and context: compare actual code with legacy docs and stakeholder notes to surface gaps.
  • Artifact generation: produce PRD/SDD-style artifacts and a reality summary stored under grimoires/loa.
  • Automation-ready outputs: outputs suitable for ingestion into the Loa workflow and future automation.

Quick Start

Run the ride skill against your repository to extract code reality into grimoires/loa/reality and generate ground-truth documentation.

Frequently Asked Questions about ride

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

FAQPage Schema
How do I extract API routes and data models from an existing codebase?

Code reality extraction analyzes your repository to identify API routes and data models by reading and grepping source files. It produces evidence-grounded artifacts that map these structural elements into a grimoire repository.

What is code drift analysis and how does it compare actual code with documentation?

Drift analysis compares actual codebase structures against legacy documentation and stakeholder context to surface discrepancies. It highlights gaps where implemented code reality diverges from documented expectations.

How do I generate ground-truth documentation for my software project?

Generate ground-truth documentation by extracting code reality into PRD and SDD-style artifacts stored under grimoires/loa. These outputs are grounded in code evidence, ensuring documentation reflects actual implementation.

Can I detect environment dependencies and potential dead code in my repository?

Yes, codebase analysis identifies environment dependencies and potential dead code by examining your source files. It extracts these items as risk elements into a reality summary stored within the grimoire artifacts.

Do I need Loa tooling to analyze my codebase and produce reality artifacts?

Yes, Loa tooling is required to read and grep code for producing reality artifacts. The extraction process depends on this tooling to generate outputs stored under grimoires/loa repositories.