vibe-init
Skill7 starsChanged 13 days agoNo licenceView on GitHub
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 session: reads the code, writes the documents, then an independent spec review in which a person verifies the PROVISIONAL SPEC.md. Produces CLAUDE.md and the full vibe/ folder, with a PLAN.md feature map of the existing features. DECISIONS.md starts from today — all prior decisions untracked by design.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- OpenOps-Studio/vibe-driven-devtheir own version, first seen Mar 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- OpenOps-Studio/vibe-driven-dev★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- vibe-add-featureSkill
- vibe-agentSkill
- vibe-architectSkill
- vibe-brainstormSkill
- vibe-changelogSkill
- vibe-change-specSkill
- vibe-costSkill
- vibe-deploySkill
- vibe-design-mdSkill
- vibe-designSkill
- vibe-doctorSkill
- vibe-documentSkill
- vibe-e2eSkill
- vibe-fix-bugSkill
- vibe-goldfishSkill
- vibe-graphSkill
- vibe-handoffSkill
- vibe-ledgerSkill
- vibe-modeSkill
- vibe-new-appSkill
- vibe-parallelSkill
- vibe-perfSkill
- vibe-progressSkill
- vibe-reviewSkill
- vibe-spec-reviewSkill
- vibe-testSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
52 rules. About 0 are common, 28 are distinctive, and 24 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈28
Distinctive · estimate
This author's own choices. Worth a look.
24
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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
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.