skills.rest
laionazeredo
laionazeredoCOMMUNITY
Explore all skills by this author →
GitHub

che-archeology

Infers project intent and roadmap from git history and merged pull requests.

Updated May 12, 2026
Search Tags:#documentation#roadmap#pull requests#legacy code#sdlc#git history#intent inference
One-click install
npx skills add https://github.com/laionazeredo/che-ai --skill che-archeology-laionazeredo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: che-archeology
Source: https://github.com/laionazeredo/che-ai/tree/main/skills/che-archeology
Command: npx skills add https://github.com/laionazeredo/che-ai --skill che-archeology-laionazeredo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When adopting a spec-driven workflow on an existing codebase, teams lack documented intent and roadmap artifacts. This Skill reconstructs that strategic backbone automatically by analyzing the repository's own history instead of requiring manual archaeology. ## Core Features & Use Cases - Historical Data Collection: Gathers git logs, merged PR metadata via the GitHub CLI, and early README versions as evidence sources. - Semantic Clustering: Groups commits and PRs into time windows and identifies the primary focus and milestone of each period. - Artifact Generation: Drafts intent.md (vision, problem statement, success criteria) and roadmap.md (3-5 chronological phases) for user approval before persisting. - Use Case: You inherit a two-year-old repository with no documentation. Run this Skill to reconstruct why the project was started and what major phases it went through, then align it with the Specflow SDLC. ## Quick Start Analyze this repository's git history and merged PRs to draft an intent.md and roadmap.md for my approval.

Frequently Asked Questions about che-archeology

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

FAQPage Schema
How do I reconstruct a project roadmap from git history?▼

Run git log in reverse chronological order and cluster commits into 2-4 week windows, identifying the primary focus of each. Group those windows into 3-5 high-level phases such as foundations, core features, and enhancements to form the roadmap.

How to document intent for an existing legacy project?▼

Analyze the first 10-20 commits and the earliest README versions to infer why the project started and who its target users are. Draft this as an intent document with vision, problem statement, and success criteria, then confirm with the team.

Does this require the GitHub CLI to analyze pull requests?▼

Yes, PR metadata collection uses the gh CLI command 'gh pr list --state merged' to retrieve titles, bodies, and dates. Without it, the analysis falls back to git log and README history only.

What are the limitations of inferring roadmaps from commits?▼

Inference accuracy depends on commit message quality and PR discipline; repositories with vague messages produce weaker phase reconstructions. The skill mitigates this with a user approval step before persisting any generated artifacts.

Where are the generated intent and roadmap files saved?▼

After user approval, the drafts are saved to the CHE_PROJECT_DIR, which is the project folder inside the project directory. Nothing is written to disk before the user reviews and approves the draft.

Related Skills

Explore More Software Engineering Skills→
microsoftmicrosoft
4.9k

comparison-base

Resolves the correct Git comparison base commit for branch reviews and change analysis.

Official
Advanced
Snowflake-LabsSnowflake-Labs
15

spec-driven

Plan, define, and implement features through EARS-based spec-driven SDLC phases.

Official
Advanced
guille-galloguille-gallo

review

Review code changes against coding standards and specifications.

Community
Advanced
psw7205psw7205
1

git-diagnosis

Diagnoses codebase health by cross-analyzing Git history churn, bug clusters, and contributor activity.

Community
Intermediate