deliver-issue-matt

Delivers one ready issue through implementation, verification, CI, protected merge, and cleanup.

1|Updated Jul 5, 2026
One-click install
npx skills add https://github.com/yersonargotev/packy --skill deliver-issue-matt-yersonargotev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deliver-issue-matt
Source: https://github.com/yersonargotev/packy/tree/main/bundle/skills/deliver-issue-matt
Command: npx skills add https://github.com/yersonargotev/packy --skill deliver-issue-matt-yersonargotev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Delivering an issue end-to-end involves many error-prone steps: qualifying the issue, isolating a workspace, implementing with TDD, running reviews, passing CI, merging through protected paths, and cleaning up. This Skill orchestrates that entire delivery lifecycle as a gated, evidence-bound workflow so nothing is merged without proof. ## Core Features & Use Cases - Gated delivery pipeline: Four sequential gates (qualify and isolate, implement and verify, change request and CI, integrate and clean up) with explicit completion criteria and exception briefs when blocked. - Proof bound to exact SHAs: Automated tests, manual verification, Standards and Spec review, and CI results are all bound to the exact candidate commit, with repair cycles limited to three per gate. - Protected integration and cleanup: Merges through merge queue, squash, or merge commit without rebasing or force-pushing, verifies issue closure, and removes only delivery-owned branches and worktrees. - Use Case: A maintainer points the agent at ready issue #123; the Skill qualifies it, creates an isolated worktree, implements via the vendored Matt Pocock TDD workflow, opens a pull request, waits for CI, merges through the protected path, closes the issue, and restores the operator's checkout. ## Quick Start Use the deliver-issue-matt skill to deliver ready issue #123 through implementation, verification, CI, merge, and cleanup.

Frequently Asked Questions about deliver-issue-matt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deliver a GitHub issue end-to-end with an AI agent?▼

Invoke the skill with the issue number and explicit delivery intent. It qualifies the issue against the ready-for-agent triage state, implements via a TDD workflow, opens a pull request, waits for CI, merges through the protected path, and closes the issue.

What issue trackers and platforms does this delivery workflow support?▼

It supports GitHub pull requests, GitLab merge requests, local Markdown filesystem operations, or a configured equivalent defined in the repository's docs/agents/issue-tracker.md file. Local Markdown setups also require a Git remote integration path and documented ticket-state updates.

What dependencies does the deliver-issue-matt skill require?▼

It requires the model-invoked /tdd and /code-review skills to be loadable, plus the consumer-owned files docs/agents/issue-tracker.md and docs/agents/triage-labels.md at the repository root. Missing dependencies produce an exception brief identifying the gap.

What happens when CI or review fails during issue delivery?▼

Failures are classified as transient or deterministic. Transient operations retry once unchanged; deterministic findings trigger a repair cycle that reruns the implementation workflow and all affected gates. Three repair cycles per gate is the limit before an exception brief is required.

Can this skill rebase or force-push during delivery?▼

No. Published history is kept append-only; amend, rebase, and force-push are forbidden after publication. Integration uses a merge queue, squash merge, or merge commit in that preference order, never a rebase merge.

When does the delivery workflow pause for human authority?▼

It pauses when continuation requires a product or scope decision, changed acceptance criteria, unavailable access, an irreversible external effect, or a protected-control override. Releases, deployments, and production changes always require separate explicit authority.