resolve-issue

Orchestrate GitHub spec issue resolution from analysis through pull request preparation.

413|31|Updated Mar 16, 2025
One-click install
npx skills add https://github.com/gittower/git-flow-next --skill resolve-issue-gittower
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-issue
Source: https://github.com/gittower/git-flow-next/tree/main/.claude/skills/resolve-issue
Command: npx skills add https://github.com/gittower/git-flow-next --skill resolve-issue-gittower

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp__github__get_issue.

What problem does it solve?

This Skill orchestrates the full lifecycle of resolving a GitHub spec issue by turning a written specification into an implementation plan, validated tests, code changes, reviews, and a publish-ready pull request.

Core Features & Use Cases

  • Spec validation: Confirms the issue is a true spec issue before any work begins.
  • Sequential orchestration: Spawns fresh subagents for analysis, planning, test validation, implementation, review, and PR summary creation.
  • Guardrailed delivery: Enforces test-first development, branch/worktree setup, review gates, and explicit publish approval.
  • Use case: Use this Skill when you need an AI system to take a GitHub spec issue from analysis through implementation and PR preparation with strong workflow discipline.

Quick Start

Use the resolve-issue skill to resolve issue number 42 end-to-end and prepare the branch for review.

Frequently Asked Questions about resolve-issue

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

FAQPage Schema
How do I resolve a GitHub spec issue end-to-end from analysis to pull request?

To resolve a GitHub spec issue end-to-end, the Skill orchestrates spec validation, sequential subagent execution for planning and test validation, code implementation, review gating, and final publish readiness checks before preparing the pull request.

Can I automate test-first development and branch management for GitHub issues?

Yes, you can automate test-first development and branch management. The Skill enforces guardrailed delivery by spawning subagents for test validation, handling worktree setup, and applying review gates before publishing changes.

Does this workflow require a GitHub issue dependency to start planning?

Yes, the workflow requires the mcp__github__get_issue dependency to fetch the GitHub issue. It validates the issue as a true spec issue before initiating any worktree handling or implementation planning.

What is the best way to ensure review gating before publishing a pull request?

The best way to ensure review gating is through sequential subagent execution that enforces explicit publish approval. The Skill checks publish readiness and applies review gates after test-first implementation and code changes.

How does spec validation work before implementing code changes?

Spec validation works by confirming the GitHub issue is a true spec issue before any work begins. This guardrailed process prevents non-spec issues from entering the sequential orchestration pipeline for implementation.