next-github-issue

Fetch the oldest open GitHub issue and implement it via the /feature skill.

Updated Sep 8, 2022

Search Tags:#automation #workflow #github #orchestration #issue-management #feature-implementation

Ready to run

npx skills add https://github.com/WouterWisse/wouterwisse.com --skill next-github-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: next-github-issue
Source: https://github.com/WouterWisse/wouterwisse.com/tree/main/.claude/skills/next-github-issue
Command: npx skills add https://github.com/WouterWisse/wouterwisse.com --skill next-github-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the identification and end-to-end implementation of the oldest open GitHub issue, reducing manual triage and handoffs.

Core Features & Use Cases

Orchestrates retrieval of the oldest open GitHub issue via GitHub CLI and filters blocked issues.
Composes a detailed user story and delegates implementation to the /feature skill, with subagents handling research, planning, and execution.
Links the resulting PR to the issue and provides a completion report with next steps.

Quick Start

Fetch the oldest open GitHub issue and automatically start the end-to-end implementation workflow via the /feature skill.

Frequently Asked Questions about next-github-issue

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

FAQPage Schema

How do I automate the implementation of the oldest open GitHub issue?▼

To automate the oldest open GitHub issue, this skill fetches it via GitHub CLI, filters blocked items, and delegates the end-to-end implementation to a feature-driven workflow, linking the resulting PR back to the issue.

Can I automatically create a pull request from a GitHub issue?▼

Yes, you can automatically create a pull request from a GitHub issue by triggering this workflow, which delegates research and execution to subordinate agents and links the resulting PR directly to the original issue.

How does automated issue triage handle blocked GitHub issues?▼

Automated issue triage filters blocked GitHub issues during retrieval, ensuring only actionable issues proceed to the feature-driven implementation workflow composed of research, planning, and execution phases.

Does this automated feature implementation workflow require manual pull request linking?▼

No, it does not require manual pull request linking. The workflow automatically links the resulting PR to the original GitHub issue and provides a completion report with next steps.

What is the best way to orchestrate end-to-end GitHub issue resolution?▼

Orchestrating end-to-end GitHub issue resolution is best handled by delegating research, planning, and execution to subordinate agents within a structured feature-driven workflow that composes detailed user stories.

Are there limitations to automating GitHub issue implementation for complex feature requests?▼

A limitation of automating GitHub issue implementation is that it delegates work to a defined feature-driven scope, meaning extremely complex feature requests may require manual intervention beyond the automated workflow's composed user stories.