Review, commit, and publish work

Review, commit, and push feature with quality gates enforced

Teams shipping features via automated review-commit-PR workflow with guardrails against premature merge.

• · Feature name (for branch/plan lookup)

• · Git commit with co-author trailer
• · Pushed branch (git push -u)
• · Created PR with title from dev/plans/<feature>.md
• · CI monitoring loop until all checks pass (max 30 iterations, 30 min timeout)

• · code-simplifier skill
• · code-reviewer agent (fallback)
• · naming-auditor agent (fallback)
• · verify-package skill (fallback)
• · git
• · gh (GitHub CLI)

• · dev/plans/<feature-name>.md exists (title/context)
• · Feature branch checked out
• · Changes staged (not committed)

• · Code review finds issues 3+ times on same problem — stops and asks user
• · Design changes required per review comments — stops (doesn't auto-merge)
• · CI fails 3 times same issue — stops (doesn't retry)
• · PR already merged — cleanup still runs (git checkout main, git pull, worktree remove)

• · Max 3-iteration review cycle (prevents review looping)
• · Fallback chain: skill → agent → manual checklist
• · Stops on design changes (doesn't decide architecture)
• · Explicit cleanup only-after-merge rule