Explain repository evolution as a reasoning trace from source order.
npx skills add https://github.com/Mikeys-Tech-Lab/poc --skill evolution-arc
Please help me install this Agent Skill. Skill: evolution-arc Source: https://github.com/Mikeys-Tech-Lab/poc/tree/main/.cursor/skills/evolution-arc Command: npx skills add https://github.com/Mikeys-Tech-Lab/poc --skill evolution-arc
It solves the problem of not knowing how a workspace’s structure, decisions, and guidance evolved over time—especially when you need an inspectable, rationale-first explanation instead of guessing.
Ask the assistant to run the evolution-arc skill to explain how this workspace got shaped the way it is, using the repo-local trace sources.
High-intent search queries and answers about installing and using this skill.
Tracing decision rationale in repository history involves reconstructing chronology into a reasoning trace, explaining what changed and why. It separates observation from inference to provide an inspectable path across guidance and implementation artifacts.
Providing ADR context for workspace evolution uses a guided source order to explain decision tensions and unresolved issues. It turns raw timeline events into rationale-first storytelling, grounding claims in traceable repo-local sources.
Getting a step-by-step explanation of workspace structure requires segment-by-segment storytelling of the repo's evolution. It directs you through curated trace surfaces to reconstruct chronology and identify the tensions shaping implementation artifacts.
Adapting technical detail for repo history explanations uses register-based delivery to switch between Everyday, Orientation, and Practitioner voices. This changes the level of detail provided without altering the factual reasoning trace.
Handling gaps in decision reasoning traces requires transparent separation of observed facts from inferred conclusions. The process explicitly identifies missing context and unresolved issues rather than guessing the rationale.
Tracing workspace evolution optionally supports Mermaid diagrams to improve understanding of the reasoning trace. These visual aids are applied when they help clarify the chronology and decision tensions shaping the repository.
Soul-Brews-StudioSearch Git history, local repositories, and Oracle memory for project traces.
HermeticOrmusAudit codebases for documentation, navigation, naming, and environment setup gaps.
dtyqExtract system architecture details from codebases into navigable Wiki pages with Mermaid diagrams.
PackmindHubGenerate Git commit messages combining GitMoji prefixes with Conventional Commits and Co-Authored-By for AI-assisted commits.
