cpp

Commit, push, and create a pull request for the current work.

This is the combined workflow for /zen:commit, /zen:push, and /zen:pr. Execute the same safety rules from those workflows in this order:

1. Commit phase:

   • Inspect git status --short, git diff, git diff --staged, and recent commit messages.

   • Stage only relevant files by explicit path.

   • Run available verification checks before committing.

   • Create one atomic commit with an appropriate message and this trailer:

     Co-Authored-By: Claude Opus 4.7 <[email protected]>

2. Push phase:

   • Confirm the current branch.
   • Do not push directly to main or master unless the user explicitly confirms that exact branch push.
   • Push to origin, creating upstream tracking with git push -u origin <current-branch> if needed.
   • Never force push.

3. PR phase:

   • Determine the base branch, preferring the repository default branch from gh repo view --json defaultBranchRef when available.
   • Read .github/PULL_REQUEST_TEMPLATE.md; stop if it is missing.
   • Review git diff <base-branch>...HEAD and the branch commits.
   • Fill the PR body according to the template, preserving its headings and checklist structure.
   • Create the PR with gh pr create.

Do not skip verification, hooks, or safety checks. If any phase fails, stop after explaining the blocker and do not continue to later phases.

Finish by reporting:

• Commit hash and message.
• Pushed branch and remote.
• PR URL.
• Verification commands run.

Arguments from the user, if any, are additional guidance for commit scope, PR title, draft mode, reviewers, labels, or base branch:

$ARGUMENTS