atmos-new-pr-mergelisted

# Atmos new-PR-merge Ship **finished** product feature work or bugfixes via a **PR-first** path so `main` stays clean and every product change leaves a PR archive. ## When to use - Small/medium feature or bugfix is done (or about to be committed) - User wants: branch → PR (template) → merge → back on latest `main` - User wants PR history even when they will self-merge immediately ## When **not** to use - Large multi-reviewer work that should stay open for review (`merge=false` only if they still want the PR opened) - Release / deploy / version-tag flows → use the dedicated release/deploy skills - Spec-only planning work with no code yet - User only wants a local commit (no remote) - **Agent skill-only edits** under `.agents/skills/**` (especially `atmos-*` skills) that only need to be published to remote — use the **direct main path** below instead of opening a PR ## Defaults | Item | Default | |------|---------| | Base / merge target | `main` (override with `base`) | | Merge after PR | **yes** (`merge=true`) | | Merge strategy | `gh pr merge --merge` (merge commit; keeps PR node in history) | | Delete remote branch after merge | **no** (keep the feature branch; use `delete_branch=true` only if asked) | | End state | local `main` (or `base`) checked out + `git pull` | ## Hard rules 1. **Never** `git commit` / `git push` on `main` for **product** work (apps/packages/crates/e2e/product docs). Product changes always go through a feature branch + PR. 2. **Exception — age