agentleFS
Sign inStart free
hardness1020hardness1020/VibeFlow/.claude/skills/analyze-codebase/SKILL.md

analyze-codebase

Skill8 starsChanged 8 months agoMITView on GitHub

Codebase discovery and analysis for Stage B of the VibeFlow docs-first workflow

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After completing Stage B, update docs/workflow-state.yaml:

    line 73
  2. Distinctive:

    After completing this stage, ask the user for permission before committing:

    line 80
  3. Very specific:

    After the commit is complete, directly run /manage-work advance <ID> to advance to the next stage.

    line 91

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

analyze-codebase

Codebase discovery and analysis for Stage B of the VibeFlow docs-first workflow.

Purpose

This skill creates Discovery documents for Stage B:

  • Analyze existing specs and code
  • Validate spec-code alignment
  • Map dependencies and side effects
  • Identify reusable components

Workflow

Stage B: Discovery
    │
    ├── Analyze existing specs and code
    ├── Validate spec-code alignment
    ├── Map dependencies and side effects
    └── Identify reusable components

Usage

Create Discovery Document

/analyze-codebase <ID>

Creates docs/discovery/disco-<ID>.md with all 5 phases.

Example:

/analyze-codebase 030

Document Requirements

Discovery (docs/discovery/disco-<ID>.md)

Required phases:

  • Phase 0: Spec Discovery (analyze existing specs)
  • Phase 1: Spec-Code Validation (verify accuracy)
  • Phase 2: Test Impact Analysis (test update checklist)
  • Phase 3: Dependency & Side Effect Mapping
  • Phase 4: Reusable Component Discovery
  • Risk Assessment & Go/No-Go Recommendation

Validation

  • scripts/validate_discovery.py — Validate discovery document

References

See references/:

  • discovery-guide.md — Discovery phases guide

Manifest Update

After completing Stage B, update docs/workflow-state.yaml:

  • Set stage: B
  • Set docs.discovery: docs/discovery/disco-<ID>.md

Git Commit

After completing this stage, ask the user for permission before committing:

git add docs/discovery/disco-<ID>.md docs/workflow-state.yaml
git commit -m "feat(discovery): codebase analysis for <slug> (#ft-<ID>)"

Replace <ID> and <slug> with actual values.

Auto-Advance

After the commit is complete, directly run /manage-work advance <ID> to advance to the next stage.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free