Submit

Compatibility submit entry point. Epic orchestration uses dedicated PR lifecycle skills.

Process

1. Pre-flight:
   • Verify you're on a feature branch (not main/master)
   • Check for uncommitted changes — commit or warn
   • Ensure branch is pushed to remote
   • Pre-PR verification — this is mandatory. Confirm clean post-implementation review evidence exists; run create-tests if the Testing Contract requires test groups not yet present; then run verify — all Testing Contract command lines plus the local-CI runner scope (repo-local gates + broader checks). Do NOT skip this step.
2. For epic workflows, route child ticket branches to submit-ticket-pr and epic branches to submit-epic-pr.
3. Report the branch, commit range, review evidence, and verification evidence (incl. repo-local + broader checks).

Key Rules

• Never force-merge or use --admin without explicit user approval
• Do not create PRs or merge branches from this compatibility skill.
• Leave PR lifecycle work to dedicated epic workflow skills.

Epic Workflow Submit Policy

submit is a compatibility entry point. Epic workflows must use:

• submit-ticket-pr for child ticket branches targeting the epic branch.
• submit-epic-pr for the epic branch targeting main/master.

Auto-merge is disabled by default. Do not run gh pr merge --auto from this skill. Child PRs may still be squash-merged into the epic branch by submit-ticket-pr after clean fresh-context review and local CI-equivalent checks. Epic PRs are opened by submit-epic-pr and left open for existing GitHub Actions and review.