workflow-commit-and-prlisted

# Workflow: Commit and PR (pre-merge orchestration) **Announce at start:** "I'm using the workflow-commit-and-pr skill to {commit / draft a PR / ship this branch}." ## When to invoke - The user wants to commit staged changes ("commit this", "make a commit"). - The user wants to create a PR ("open a PR", "ship this", "create a pull request"). - The user announces feature completion ("I'm done", "I finished the feature", "feature is complete") — preview-only mode. - The user references a ticket key (`[A-Z]+-\d+`, atlassian/Confluence/GitHub URL) AND wants to commit/PR — chains `swe-workbench:ticket-context` first. ## When NOT to invoke - The PR is already merged → use `swe-workbench:workflow-cleanup-merged` for post-merge cleanup. - The user wants to amend or rebase an existing commit → out of scope; do not amend or force-push. - The user is staging files only (`git add`) with no commit intent → no skill needed. - `workflow-development` Phase 5 is currently driving the flow → that path invokes `swe-workbench:workflow-commit-and-pr` directly (do not interpose). ## Trigger-phrase discipline The user's exact phrasing determines what action you take. **Never escalate without explicit user words.** | Phrase class | Examples | Action | |---|---|---| | **Preview only** | "I finished the feature", "I'm done", "feature is complete", "ready to commit" | Show: diff summary, drafted commit message, current branch name, doc-only `[no ci]` check. **Do NOT commit.** Wait for user to e