agentdev-workflow-case-close

Orchestrates PR squash merge, QG-4 final acceptance, and Issue closure for GitHub Cases.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/yogata/agent-dev-flow --skill agentdev-workflow-case-close-yogata
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentdev-workflow-case-close
Source: https://github.com/yogata/agent-dev-flow/tree/main/src/opencode/skills/agentdev-workflow-case-close
Command: npx skills add https://github.com/yogata/agent-dev-flow --skill agentdev-workflow-case-close-yogata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Closing a development Case involves many error-prone steps: merging the PR safely, verifying completion criteria, promoting Design documents, cleaning up worktrees and branches, and capturing learnings. This Skill automates that entire close-out workflow so nothing is skipped or done out of order. ## Core Features & Use Cases - PR Merge & Conflict Handling: Performs squash merge to main with mergeable UNKNOWN polling, ahead-commit detection, and Level 1 rebase conflict resolution. - QG-4 Final Acceptance Gate: Evaluates and updates Issue completion checkboxes, runs docs verification, distribution-boundary gates, and independent traceability re-checks before merge. - Epic Wave Close: Batch-merges and closes all child Issues of the current Epic Wave, updates the Epic status table as single writer, and determines final Wave completion. - Capture & Cleanup: Separates intake/learning captures from the PR body, deletes worktrees and branches, persists .agentdev/ state, and supports idempotent resume from durable state. - Use Case: After a PR passes review, invoke the case-close command to merge the PR, verify all completion conditions, promote draft Designs to accepted, close the Issue, and record learnings in one controlled flow. ## Quick Start Run the /agentdev/case-close command with the Issue number to merge its PR and complete the Case.

Frequently Asked Questions about agentdev-workflow-case-close

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

FAQPage Schema
How do I merge a PR and close a GitHub Issue in one workflow?▼

Invoke the case-close command with the Issue number. The workflow resolves the Issue, runs the QG-4 acceptance gate, verifies docs, squash merges the PR to main, closes the Issue, and cleans up the worktree and branch.

How does the workflow handle merge conflicts during PR merge?▼

It first polls the mergeable state when GitHub returns UNKNOWN, then attempts a Level 1 mechanical rebase for conflicts. If the rebase itself conflicts, it escalates to the case-auto command for Level 2/3 resolution and stops.

Can it close multiple child Issues of an Epic at once?▼

Yes. When given an Epic Issue with a status tracking table, it runs Epic Wave close: batch-merging and closing all running child Issues of the current Wave, updating the Epic status table as the single writer, and judging whether the Epic itself can close.

What happens if the workflow stops partway through?▼

The Case transitions to blocked with a recorded resume command. On resume, each step reconstructs its state from durable sources like Issue checkboxes, PR merge status, and commit hashes, and re-execution is idempotent so merged PRs are never re-merged.

Why does the workflow avoid the --delete-branch flag when merging?▼

Using --delete-branch fails to delete the local branch when it is checked out in an active worktree, which prevents remote deletion from running. Branch deletion is instead performed as a separate dedicated step after the merge.