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:49
优化了前置检查流程描述,明确了使用批准命令建立基线,并将产品文档与仓库指令的审查顺序标准化。
- b00eb84 2026-09-08 23:13


