issue-driven-development

Convert a GitHub issue into a pull request with validated acceptance criteria.

Updated May 17, 2022
One-click install
npx skills add https://github.com/kanade0404/dotfiles --skill issue-driven-development-kanade0404
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-driven-development
Source: https://github.com/kanade0404/dotfiles/tree/main/.opencode/skills/issue-driven-development
Command: npx skills add https://github.com/kanade0404/dotfiles --skill issue-driven-development-kanade0404

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the manual overhead of taking a GitHub issue from intake to a pull request, while enforcing clear acceptance criteria and safe escalation when the request is too vague.

Core Features & Use Cases

  • Headless issue processing: Handles labeled issues, manual issue references, and routine-driven selection of ready work.
  • End-to-end execution: Creates a branch, implements the change, runs tests locally, commits, pushes, and opens a PR.
  • Guardrailed outcomes: Stops on ambiguous requirements, records escalation context, and separates PR creation from later CI or review responses.
  • Use case: A maintainer can point the agent at a ready issue and get back a reviewable PR without supervising each step.

Quick Start

Ask the agent to process a specific GitHub issue through the issue-driven-development workflow and create a pull request when the work is complete.

Frequently Asked Questions about issue-driven-development

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

FAQPage Schema
How do I automate turning GitHub issues into pull requests?

You can automate turning GitHub issues into pull requests by validating acceptance criteria, creating a branch, implementing the change, running tests locally, and opening a PR automatically.

Can I automatically create a branch and implement changes from a labeled GitHub issue?

Yes, you can automatically create a branch and implement changes from a labeled GitHub issue by pointing an agent at the issue, which then handles the end-to-end execution from branching to pushing and opening a reviewable PR.

What happens if a GitHub issue lacks clear acceptance criteria during PR automation?

If a GitHub issue lacks clear acceptance criteria during PR automation, the workflow applies strict gatekeeping by stopping on ambiguous requirements, recording escalation context, and halting implementation until the request is clarified.

Does issue-driven development handle CI repair and code review responses?

No, issue-driven development does not handle CI repair or code review responses. The workflow strictly separates PR creation from later CI repair or review response workflows to maintain guardrailed outcomes.

Do I need to manually select ready GitHub issues for branch creation and PR automation?

No, you do not need to manually select ready GitHub issues. The workflow supports routine-driven selection of open work in repository automation, alongside processing labeled issues or direct owner/repo issue references.