Submit-PR Recipe

Say “Ship It”
and Walk Away

One command replaces the entire PR workflow.
Come back to a merged PR or a clear escalation.

Active

v2.0.0 · Amplifier Workspaces

The Reality

14 manual steps you know by heart

1 Create feature branch (if on main)

2 Write a good commit message

3 Stage and commit changes

4 Fetch and merge base branch

5 Resolve merge conflicts

6 Check documentation requirements

7 Update changelog/docs if needed

8 Push to remote

9 Create PR with good description

10 Wait for CI checks

11 If CI fails: debug, fix, push, repeat

12 Merge when ready

13 Delete local branch

14 Pull latest main

The Insight

None of this is hard.
It’s just tedious.

14

Steps

Each one simple. Together, they fragment your focus.

3×

CI Retries

When that flaky test fails at 5pm Friday.

?

Forgotten

Wrong base branch. Missing docs. Human error.

The Transformation

One command. Everything handled.

Before

14

manual steps

→

After

1

command

Under the Hood

3 steps automate everything

bash

Safety Check

Validates branch targets, reads repo config, detects base branch

Forbidden branch protection Auto-detect main/master Git state capture

agent

Workspace Cleanup

Reviews code quality before submission

Temp file detection Philosophy compliance Component size check

agent

PR Orchestration

The heavy lifter: branch, commit, PR, CI, merge, cleanup

Smart commit messages Conflict resolution PR standards discovery CI monitor/fix loop Auto-merge

The Secret

Intelligence, not just scripting

Some things need rules. Some things need judgment.

Bash for Determinism

Git commands, status checks, config reading. Rules are absolute here. No AI judgment needed.

Agents for Judgment

Commit messages, conflict resolution, CI fixing, PR descriptions. These need reasoning.

Specialized Delegation

zen-architect writes commits. bug-hunter fixes CI. explorer discovers PR standards.

Quality Gates

6 checks before your code ships

🛡

Branch Protection

Can’t accidentally PR to forbidden branches

🔎

Code Quality

No debug artifacts, TODOs, or temp files

🧠

Philosophy Compliance

Matches project conventions and patterns

📄

Documentation

Required docs are present and updated

✅

PR Standards

Learns from recent PRs in your repo

🔄

CI Monitoring

Watches, diagnoses, fixes (up to 3 attempts)

Trust Through Transparency

Knows when to proceed.
Knows when to ask.

Handles Automatically

Proceeds

Simple merge conflicts (whitespace, imports)
Creating branches and commits
Fixing common CI failures
Merging when all checks pass
Cleaning up branches after merge

Escalates to You

Asks

Complex conflicts (semantic changes)
CI failures after 3 fix attempts
Required reviewers or approvals
Blocking code quality issues
Unknown error conditions

This is why it builds trust. It won’t blindly push through problems.

Real-World Refinement

The “Analysis Paralysis” Bug

The Problem

The recipe kept freezing, unable to proceed. Why?

Two steps gave contradictory signals:

safety-check: “has_uncommitted_changes: true”

workspace-cleanup: “nothing to commit”

The cleanup agent was dismissing untracked work files as “not production code” when they were the actual deliverables.

The Fix

Clarified separation of concerns:

workspace-cleanup: Checks code quality only. Never assesses what to commit.

safety-check: Source of truth for git state. Determines what needs committing.

Lesson: In multi-agent systems, clear boundaries prevent analysis paralysis.

By the Numbers

What this actually means

14

steps automated

6

quality checks

3

specialized agents

1

command

Sources

Research Methodology

Data as of: February 20, 2026

Feature status: Active (Amplifier Workspaces)

Recipe version: v2.0.0

Research performed:

File search: find across amplifier-bundle-recipes and .amplifier/cache for submit-pr files
No standalone recipe file found — this is an integrated Amplifier Workspaces capability
Deck content based on existing documented behavior of the submit-pr workflow

Primary contributor: Amplifier Workspaces team

Gaps: No dedicated recipe YAML file to analyze; step counts and quality gates are from the documented workflow design, not measured from code.

Note: The “Analysis Paralysis” bug story is from real-world usage, documented in the original deck.

Get Started

Just say the words

“ship it”

“submit pr”

“create pr”

Walk away. Come back to a merged PR
or a clear escalation.

Amplifier Workspaces · submit-pr recipe v2.0.0

Say “Ship It”and Walk Away