ship-subissue

Installation
SKILL.md

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

Installs
2
First Seen
Sep 7, 2026
ship-subissue — quantumquirkxyz/skills-quirk