Ship It, Walk Away

One command for the whole PR lifecycle

The Frame

Shipping a PR is a chain of small mechanical steps — and the chain is the problem

Branch off the right base, keep docs compliant, follow repo standards, watch CI, wait for approval, merge, resolve conflicts, clean up. Each step is simple.

But stacked together they fragment focus and invite human error. /git:submit-pr exists to carry that whole chain for you.

1Branch off the right basethen keep docs compliant
2Follow repo standardsthen watch CI, wait for approval
3Merge, resolve conflictsthen clean up

The Proof

This isn't a concept — PR #10 owns the end-to-end lifecycle

PR #10 transformed /submit-pr “from a simple PR creation tool into a full lifecycle management system that handles everything from branch creation to merge and cleanup.”

A merged, dated, verbatim quote — so where does the rest of the lifecycle come from?

#10

Merged 2025-12-09 (kenotron-ms), 5 files changed

simple → full

PR-creation tool → full lifecycle management system

The Project

Built in the open in kenotron-ms/amplifier-setup

/git:submit-pr is a Claude Code slash command in the ‘git’ plugin. It was built progressively across seven merged PRs — #6, #7, #10, #12, #13, #14, #18 — between Dec 4 and Dec 20, 2025.

Authored by Ken Chau (kenotron-ms) and Johanna Hawkins (johannao76). Now, how it removes each step.

7

Merged PRs (#6, #7, #10, #12, #13, #14, #18)

2

Authors: Ken Chau & Johanna Hawkins

90

Total commits in the analyzed window; plugins: 15

Mechanism — Before the PR

Step 3 enforces documentation compliance before a PR ever opens

A mandatory automatic gate (PR #7) discovers CONTRIBUTING.md, MAINTENANCE.md and CLAUDE.md, uses a general-purpose agent to update docs, and runs required linting, testing and type checking.

Compliance is enforced by deterministic rules, not memory. Next: watching CI once the PR is open.

•Always runs before PR creationStep 3: “Ensure Documentation Compliance (Automatic)”
•Discovers repo doc standardsCONTRIBUTING.md, MAINTENANCE.md, CLAUDE.md
•Runs required commandslinting, testing, type checking

Mechanism — While It's Open

Real-time monitoring watches CI and auto-merges the moment it's green

Full lifecycle automation (PR #10) watches CI/CD checks and approval status with live updates every 10 seconds, and auto-merges when approved and all checks pass.

The tedious ‘watch, wait, merge’ step is offloaded. But what about the step that isn't mechanical?

10s

Live updates on CI/CD and approval status

auto

Merges when approved and all checks pass

Mechanism — Conflicts

When conflicts appear, PR #18 gives the command judgment

Intelligent merge-conflict resolution: deep analysis with the Task tool and commit-history review, simple/complex categorization, and evidence-based resolution using CI artifacts.

An autonomous fix-verify-merge loop — up to 3 retries — completes the case that the whole lifecycle is covered.

Deep analysis — Task tool with commit-history review
Categorization — simple vs complex conflicts
Evidence-based — resolution using CI artifacts
Fix-verify-merge loop — up to 3 retry attempts

The Payoff

PR #12 made it fully hands-off — say ‘ship it’ and walk away

A PR-submission skill triggers /submit-pr on natural language like “create a PR” or “ready for review” — no confirmation needed, completely hands-off — and enables auto-merge immediately on PR creation.

You walk away and come back to a merged PR. One spoken intent replaces the whole chain.

# plain language, no confirmation
“create a PR”
“ready for review”

# skill triggers
/submit-pr
# auto-merge enabled on creation
# → you come back to a merged PR

The Takeaway

Determinism for rules, judgment for conflicts, honest escalation for the rest

GitHub native auto-merge runs on creation, with a manual-merge fallback (Step 7b) when auto-merge is unavailable — autonomous regardless of repo settings.

And when the retry loop can't resolve a conflict, it falls back to guided human intervention. Autonomous without pretending to be infallible.

Determinism — compliance & standards discovery by rule
Judgment — agent conflict analysis via the Task tool
Fallback — manual merge (Step 7b) when auto-merge is unavailable
Escalation — guided human intervention when retries run out

Sources

Sources & Research Methodology

Shipped & merged

Data as of: 2026-07-05 corpus snapshot of kenotron-ms/amplifier-setup.

Feature status: Shipped and merged; built across PRs #6, #7, #10, #12, #13, #14, #18 (2025-12-04 → 2025-12-20). Latest capability: intelligent merge-conflict resolution (PR #18). Personal Claude Code plugin repo, not a microsoft/* core repo.

Research performed:

Source repo verification: ls /home/ramparte/dev/ANext/bkrabach and find . -maxdepth 3 -iname '*recipe-executor-ux*' (not found) — corrected source to kenotron-ms/amplifier-setup
Capability grep: grep -rl 'submit-pr' corpus → kenotron-ms__amplifier-setup sources; module lists plugins/git/commands/submit-pr.md
Per-PR verbatim quotes, dates, authors and file counts grepped from _sources/kenotron-ms__amplifier-setup-2026-07-05-changes.md (PRs #2, #3, #6, #7, #10, #12, #13, #14, #18)
Commit volume: grep 'Total commits' / 'plugins:' → 90 total commits in window; plugins: 15

Gaps: The live GitHub repo is not cloned locally; all facts trace to the corpus git-log-derived source file and its two derived notes, not a fresh git log/gh run. The suggested source bkrabach/recipe-executor-ux does not exist and was replaced. The word “recipe” is a framing choice: this is a slash command in a plugin, not an Amplifier YAML recipe.

Primary contributors: Ken Chau (kenotron-ms) — repo owner, opened PRs #1–#10, #12, #13, #17. Johanna Hawkins (johannao76) — opened PRs #11, #14, #15, #16, #18.