From qult
Branch completion workflow. Use when implementation is complete and all tests pass — guides the architect through merge, PR, hold, or discard options. NOT for incomplete work or failing tests.
npx claudepluginhub hir4ta/qult --plugin qultThis skill uses the workspace's default tool permissions.
Structured branch completion. Present options, execute the architect's choice.
Guides strict Test-Driven Development (TDD): write failing tests first for features, bugfixes, refactors before any production code. Enforces red-green-refactor cycle.
Guides systematic root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
Guides A/B test setup with mandatory gates for hypothesis validation, metrics definition, sample size calculation, and execution readiness checks.
Structured branch completion. Present options, execute the architect's choice.
Proof or Block. No completion claims without fresh verification evidence. Tests pass. Review passes. Then — and only then — we finish.
Run verification before anything else:
mcp__plugin_qult_qult__get_session_status() — check test and review statusmcp__plugin_qult_qult__get_pending_fixes() — check for unresolved issuesreview.require_human_approval is enabled in .qult/config.json, check human_review_approved_at in session status. If null, add Human approval: not recorded to the BLOCKED list and instruct the architect to review the changes, then call mcp__plugin_qult_qult__record_human_approval() to record their approvalIf any gate is NOT clear:
BLOCKED: Cannot finish.
- [ ] Pending fixes: N remaining
- [ ] Tests: not passed
- [ ] Review: not completed
Fix these first, then run /qult:finish again.
Stop. Do NOT proceed to Step 2.
git branch --show-currentmain or master)Branch: feature/xyz
Base: main
Commits: N (ahead of base)
Changed files: N
Tests: PASSED
Review: PASSED (Score: N/30)
Present exactly these 4 options. No more, no fewer. No open-ended questions.
How would you like to finish this branch?
1. **Merge** — Merge into [base] and delete the branch
2. **PR** — Push and create a pull request for team review
3. **Hold** — Keep the branch as-is for later
4. **Discard** — Delete the branch and all changes
Use AskUserQuestion with these exact options. Wait for the architect's choice.
git checkout [base]git merge [branch] --no-ffgit branch -d [branch]git push -u origin [branch]gh pr create:
git checkout [base]git branch -D [branch]If the branch was a git worktree:
git worktree remove [path] (after merge/discard)