vibe-change — Claude Code skill: what it does, how to install
Adds a bounded feature to an existing project while preserving current behavior and preventing redundant planning restarts.
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-change -a claude-codeWhat vibe-change does
The skill guides an agent through shipping one bounded feature into an active codebase. Unnecessary discovery is halted immediately. It stops the model from restarting research when files like PRD or AGENTS.md are missing. Instead, the agent inspects the relevant diff and targeted files, asking questions only about missing acceptance criteria.
Modifications stay confined to the smallest possible surface area. The agent avoids unrelated refactoring. For risky edits, it records a recovery checkpoint before proceeding. It runs regression checks against modified user flows. The process wraps up with a structured report covering Changed, Checked, Not checked, Next decision, and Recovery sections.
Verification relies directly on ../vibe-verify/SKILL.md, while task progression is recorded in MEMORY.md. If those neighboring files are absent, verification and state tracking break down. The skill escalates to extensive planning only when handling security requirements or database migrations.
What it helps with
- add a bounded feature without touching unrelated code
- record a recovery checkpoint before making risky edits
- run regression checks across modified user flows
- document progress and product decisions in
MEMORY.md
Example prompts for the agent
- Add CSV report export following vibe-change rules without touching nearby modules
- Implement order list sorting and create a recovery checkpoint before modifying code
- Add avatar file size limits, update
MEMORY.md, and verify affected user flows
How to install vibe-change
1Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-change -a claude-code2Manually: put the files in place
~/.claude/skills/vibe-change/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/vibe-change/
1Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-change -a codex2Manually: put the files in place
.agents/skills/vibe-change/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-change -a cursor2Manually: put the files in place
.cursor/skills/vibe-change/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install KhazP/vibe-coding-prompt-template vibe-change2Manually: put the files in place
.github/skills/vibe-change/SKILL.md1Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-change -a gemini-cli2Platform CLI
gemini skills install https://github.com/KhazP/vibe-coding-prompt-template --path workflow/skills/vibe-changeManually: put the files in place
.devin/skills/vibe-change/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-change -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about vibe-change
How do I install vibe-change in Claude Code?
Run npx skills add KhazP/vibe-coding-prompt-template --skill vibe-change -a claude-code in your terminal.
What does the vibe-change skill do?
It enforces shipping one isolated feature in an existing app while preventing unnecessary rewrites and blocking full project research restarts.
When does vibe-change escalate to deeper planning?
It triggers extensive planning only when making decisions about architecture, security, infrastructure costs, or database migrations.
Source text
SKILL.md · MIT
--- name: vibe-change description: Add one bounded feature to an existing app while preserving current behavior. Do not restart the full new-project workflow. allowed-tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion --- # Vibe Change Inspect the affected source, applicable repository instructions, current diff, and relevant checks. Consult product documents when scope or acceptance criteria are unclear. Confirm only missing acceptance criteria, constraints, and scope. An absent PRD or AGENTS.md does not require starting research again. Establish the relevant baseline with checks appropriate to the change; use an existing user journey when behavior is affected. Preserve current work; record a real recovery checkpoint for risky changes. Identify the smallest affected area and implement one feature without unrelated rewrites. Add regression checks where they demonstrate behavior, and rerun the affected checks. Use `../vibe-verify/SKILL.md` for the changed journey and relevant existing behavior. Update product decisions only where requirements changed, and progress in MEMORY.md. Report Changed, Checked, Not checked, Next decision, Recovery. Escalate to deeper planning only for an actual architecture, security, cost, or data-migration decision.
© KhazP · MIT · KhazP/vibe-coding-prompt-template
