ride

Analyze repository code reality and generate evidence-grounded Loa artifacts.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Adeitasuna/mibestat --skill ride-adeitasuna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ride
Source: https://github.com/Adeitasuna/mibestat/tree/main/.claude/skills/riding-codebase
Command: npx skills add https://github.com/Adeitasuna/mibestat --skill ride-adeitasuna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Ride skill analyzes an existing codebase to reveal its true behavior, extract evidence-grounded Loa artifacts, and populate a grimoire-ready reality for governance and drift analysis.

Core Features & Use Cases

  • Analyze code to produce LOA-aligned artifacts such as PRD, SDD, drift reports, and reality summaries.
  • Compare code reality against existing documentation and user context to surface gaps and inconsistencies.
  • Enable maintenance handoffs by generating structured, evidence-backed outputs that include file:line citations.

Quick Start

Initiate an end-to-end reality analysis of the repository to generate grimoire artifacts for the target project.

Frequently Asked Questions about ride

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

FAQPage Schema
How do I analyze a codebase to extract concrete code reality and generate documentation artifacts?

To analyze a codebase and extract concrete code reality, this process identifies true code behavior and translates it into evidence-grounded Loa artifacts. It generates governance-ready documentation like PRDs, SDDs, and reality summaries with file:line citations.

What is code reality drift analysis and when do I need it for my repository?

Code reality drift analysis compares actual codebase behavior against existing documentation to surface gaps and inconsistencies. You need it to enforce evidence grounding and maintain accurate, governance-ready documentation across large repositories.

Can I generate PRD and SDD artifacts with file citations directly from my existing code?

Yes, you can generate PRD, SDD, and reality summaries directly from existing code. The process enforces evidence grounding by extracting concrete code reality and producing structured outputs that include precise file:line citations for maintenance handoffs.

How do I populate a grimoire-ready reality for project governance and drift tracking?

To populate a grimoire-ready reality, initiate an end-to-end repository analysis to extract true code behavior. This generates evidence-backed Loa artifacts and drift reports, providing governance-ready documentation with a clear maintenance handoff.

What is the best way to surface inconsistencies between documentation and codebase reality in large repos?

The best way to surface inconsistencies in large repos is by performing reality extraction and drift analysis. This compares code reality against existing documentation and user context to enforce evidence grounding and identify gaps.