vibe-change
GitHub在现有应用中安全添加单个功能,保持行为一致。通过检查代码、测试和文档,最小化变更范围,执行回归验证并记录恢复点,避免全量重构或重启工作流。
Trigger Scenarios
Install
npx skills add KhazP/vibe-coding-prompt-template --skill vibe-change -g -y
SKILL.md
Frontmatter
{
"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.
Version History
-
db48176
Current 2026-09-22 04:50
优化了工作流程描述,精简了对仓库指令和文档的检查要求,强调使用已批准命令建立基线。
- b00eb84 2026-09-08 23:13


