메뉴
Fully autonomous development workflow from prompt to commit. Chains spec → develop → review → commit. Triggers: /vibe, 'vibe this', 'autonomous workflow', 'just do it all', 'build this end-to-end', 'full pipeline', 'handle everything'.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | vibe |
| description | Fully autonomous development workflow from prompt to commit. Chains spec → develop → review → commit. Triggers: /vibe, 'vibe this', 'autonomous workflow', 'just do it all', 'build this end-to-end', 'full pipeline', 'handle everything'. |
| allowed-tools | Bash, Read, Glob, Skill |
| argument-hint | <prompt> [--dry-run] |
| user-invocable | true |
Full pipeline (spec → develop → review → commit) from a single prompt.
<prompt> — what to build (required)--no-review — skip review stage--dry-run — spec only, stop before developNo prompt → tell user: /vibe <what to build>, stop.
Stage numbering [N/M]: M = total stages that will run. Base: 5 (spec, develop, review, commit, report). --no-review → 4. --dry-run → 1.
Output [1/M] Spec.
Skill("spec", args="<prompt> --auto")
Spec runs silently with --auto and returns both spec and plan file paths. Read the plan file path from the output or find via ct plan latest.
Verify the plan file exists and has content. Immediately proceed to develop.
Output [2/M] Develop.
If --dry-run → stop here. Report the plan file path, suggest /develop <path>.
Skill("develop", args="<plan-file-path> --auto")
Verify all workers completed. If some failed, report per-worker status and stop.
Bugfix detection: If the spec mentions "bug", "fix", "regression", or includes reproduction steps — after develop completes, re-run the reproduction scenario to confirm the fix works. If reproduction still fails, report and stop (do not proceed to review with a broken fix).
Immediately proceed to review.
Output [3/M] Review.
Skip if --no-review.
Skill("crit")
Fix any critical issues inline. Immediately proceed to commit.
Output [4/M] Commit.
If git diff --stat is empty → skip.
Skill("commit")
Output [M/M] Report.
Skill("report")
Generates a post-implementation summary in ~/blueprints/. Runs silently — failure here doesn't block the pipeline.
Report: one line per stage (completed / skipped / failed).
If a stage fails with zero progress:
/<failed-skill> [args] to retry the failed stageSystematic root cause investigation before proposing fixes. Triggers: bugs, test failures, unexpected behavior, 'why is this failing', 'not working', 'broken'.
Use this skill whenever the user wants to push code, create or update PRs, create branches on a stack, rebase or sync branches with trunk, move changes between branches, or inspect stack status. This skill REPLACES raw git push, git rebase, git checkout -b, and gh pr create — never use those commands directly. Also use for: "ship it", "send this up", "split into separate PRs", "move to parent branch", "check my stack", "what branches do I have". Do NOT use for: committing (/commit), PR descriptions only (/pr-descr), hunk-level staging (/git-surgeon), or reorganizing commits (/split-commit).
Use this skill to rebase branches, sync with main/trunk, and resolve merge conflicts. REPLACES git rebase — never use it directly. Triggers: 'restack', 'rebase', 'rebase on main', 'sync with main', 'update stack', 'resolve conflicts', 'branches out of date'.
Use this skill to push code to remote and create or update PRs. REPLACES git push and gh pr create — never use those directly. Triggers: 'push', 'push my changes', 'ship it', 'send this up', 'submit', 'update PRs', 'create PR', 'push stack', 'send PRs'.
Quick adversarial code review — cleanup pre-pass + 2 focused reviewers. Default for everyday reviews. Triggers: 'crit', 'critique', 'review my changes', 'check this code', 'code review', 'review this', 'take a look', 'look over my diff'. Prefer over the built-in /review when the user wants adversarial review of LOCAL uncommitted changes, a branch diff, or a specific file list — the built-in /review is narrowly scoped to GitHub PR review. For deep multi-perspective review use /superreview.
Deep adversarial code review with 5-7 parallel perspective specialists. Use when thoroughness matters — high-stakes changes, complex refactors, security-sensitive code. Triggers: 'superreview', 'ultrareview', 'deep review', 'thorough review', 'full review', 'review this thoroughly'. Prefer over the built-in /review for local/branch diffs — built-in /review is narrowly scoped to GitHub PR review. For quick reviews use /crit instead.