Ship Subissue

Contract

• Input: problem or task defined by the skill body.
• Output: Markdown artifact or structured result with completion criteria met.
• Side effects: none (design/review/documentation only unless explicitly stated).
• Dependencies: none (self-contained unless linked to other skills).
• Stop condition: all process steps completed; artifact saved; criteria checked.
• Risk: low.
• Boundary: produces reasoning or documentation artifacts; does not modify external systems unless explicitly instructed.

Ship Subissue

Merge one approved repository-local subissue PR, including a corrective subissue PR, mark the subissue as completed, and close out the linked issue when needed. Use the canonical work-item format in docs/agents/work-item-format.md when deciding what metadata to preserve: linked-issue labels and milestone are the source of truth, and the completion note should not introduce conflicting tracker metadata.

Workflow

1. Confirm the target.
   • Read the open PR with gh pr view.
   • Confirm the PR still belongs to the current branch and subissue.
   • Confirm the linked issue reference is clear.
   • Confirm the branch is clean and no conflicted branch state remains from merge/rebase or review-request follow-up work; if it is conflicted, return to resolving-merge-conflicts before shipping.
2. Confirm review is clean.
   • Only proceed if the last review-pr pass was clean on both Standards and Spec.
   • If review is not clean, stop and return to review-fix-loop.
3. Merge the PR.
   • Use gh pr merge <number> with the repository's accepted merge strategy.
   • Delete the branch if the repository convention allows it.
4. Close or complete the issue.
   • If the workflow uses an explicit completion state, update it to reflect that the subissue is done.
   • If GitHub does not auto-close the linked issue, close it with gh issue close <number> --comment "Merged in PR #<number>."
   • Do not guess the issue number.
5. Record completion.
   • Leave a short note on the PR or issue summarizing the merge and completion state.

Guardrails

• Never merge with unresolved review findings.
• Never mark an issue complete unless the linked reference is clear.
• Never delete the branch before the merge has succeeded.