ship-issue

Automating an end-to-end issue workflow from triage to merge involves reading and labeling issues, generating agent briefs, writing tests, implementing minimally, running local CI replication, and squash-merging. This requires explicit operator authorization to initiate.

An automated issue shipping workflow is a pipeline that takes an issue from initial triage through test writing, minimal implementation, subagent review, local CI replication, push, and CI monitoring to a final squash-merge.

To prevent direct merges to main during PR automation, use a workflow that enforces guardrails blocking direct main merges and mandates subagent coordination for tests and reviews before allowing a squash-merge.

Using subagents for code review and test writing involves delegating these tasks within an end-to-end shipping workflow, allowing a primary agent to coordinate subagent test generation and self-review before pushing changes and monitoring CI.

Yes, you can run local CI replication before pushing by incorporating it into an end-to-end shipping workflow, which executes local CI checks to validate the minimal implementation prior to pushing and monitoring remote CI.

Yes, automated issue triage to merge requires explicit operator authorization to initiate the full workflow, ensuring the operator delegates the process using specific trigger phrases to start the end-to-end pipeline.