vibe-initlisted

Onboards an existing or legacy codebase into the vibe-* skills framework. Reads actual source files, infers architecture and patterns, generates the full vibe/ folder so vibe-add-feature, vibe-fix-bug, vibe-review, and all vibe-* skills work immediately. Triggers on "vibe-init", "onboard this project", "init the vibe folder", "set up vibe for this project", "this is a legacy project", "retrofit this codebase", "I want to use vibe skills on an existing project", "add vibe to this repo", "the vibe folder doesn't exist", "can we use vibe skills here". Always use when the user has an existing codebase with no vibe/ folder and wants to use any vibe-* skill — even without the exact trigger phrases. Single agent session — reads everything, generates everything, no staged checkpoints. Produces CLAUDE.md and full vibe/ folder grounded in actual code. SPEC.md marked PROVISIONAL — verify before first vibe-review run. DECISIONS.md starts from today — all prior decisions untracked by design.
aakashdhar/vibe-skill · ★ 7 · Code & Development · score 68

Install: claude install-skill aakashdhar/vibe-skill

# Vibe Init Skill Reverse-engineers the vibe-* framework scaffold from an existing codebase. Reads actual source files. Infers everything from code. Documents only what is observed. Produces a complete vibe/ folder that immediately unblocks all vibe-* skills. **Run in agent mode (Claude Code / Cursor). Requires filesystem access.** **Single session — reads everything, generates everything, no staged checkpoints.** --- ## The contract this skill establishes **Code is the source of truth.** Nothing is invented. If it's in ARCHITECTURE.md, it was observed in the codebase. If it's in CODEBASE.md, the file exists. **The past is untracked. The future is fully tracked.** DECISIONS.md starts with one bootstrap entry dated today. Every decision made through vibe-* skills from this point forward gets logged. Prior decisions are acknowledged as unknown — not fabricated. **SPEC.md is provisional.** It describes observed behaviour, not planned requirements. It is marked clearly. vibe-review will flag it until a human verifies it. This is honest — encoding bugs as requirements is worse than flagging uncertainty. --- ## Pre-flight — confirm project root Before reading anything: ```bash pwd ls -la ``` Confirm you are at the project root (the directory containing the source code). If not, stop and ask the user to navigate there first. Check if vibe/ already exists: ```bash ls -d vibe/ 2>/dev/null && echo "EXISTS" || echo "NOT FOUND" ``` If vibe/ already exists: > "A vibe/ folder