work-issue

Automate GitHub issue implementation into code changes and pull requests.

29|4|Updated Jan 12, 2026

Search Tags:#workflow #github #branching #issue #code-implementation #pr-management

Ready to run

npx skills add https://github.com/matsen/bipartite --skill work-issue-matsen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: work-issue
Source: https://github.com/matsen/bipartite/tree/main/skills/work-issue
Command: npx skills add https://github.com/matsen/bipartite --skill work-issue-matsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read a GitHub issue and implement the work described in it, turning informal requests into concrete code changes and CI-ready PRs.

Core Features & Use Cases

Read issue bodies and comments to understand requirements and acceptance criteria.
Ask clarifying questions when requirements are ambiguous to prevent rework.
Create a feature branch, implement changes, run tests, and prepare PR documentation.
Generate a concise PR summary with notes for reviewers and potential follow-ups.

Quick Start

Pass an issue number to start the workflow, for example /work-issue 123.

Frequently Asked Questions about work-issue

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

FAQPage Schema

How do I turn GitHub issues into implemented code changes automatically?▼

To turn GitHub issues into implemented code changes, you can use a workflow that reads issue bodies and comments, asks clarifying questions, creates a feature branch, implements the code, runs pre-merge checks, and generates a PR.

Can I generate a CI-ready PR directly from a GitHub issue?▼

Yes, you can generate a CI-ready PR directly from a GitHub issue by passing the issue number to the workflow, which handles branch creation, code implementation, and PR documentation with a summary for reviewers.

What is the best way to prevent rework when implementing GitHub issues?▼

The best way to prevent rework when implementing GitHub issues is to ask clarifying questions when requirements are ambiguous, ensuring acceptance criteria are fully understood before creating a feature branch and writing code.

Do I need git and GitHub CLIs to automate issue implementation workflows?▼

Yes, you need git and GitHub CLIs to automate issue implementation workflows, as the process coordinates with these command-line tools to enforce branch creation, code changes, and PR generation steps.

How does an automated GitHub issue workflow handle PR documentation?▼

An automated GitHub issue workflow handles PR documentation by generating a concise PR summary that includes notes for reviewers and outlines potential follow-up tasks after pre-merge checks pass.

What should I do if my GitHub issue requirements are ambiguous before coding?▼

If your GitHub issue requirements are ambiguous before coding, the workflow will ask clarifying questions based on the issue body and comments to prevent rework, ensuring the feature branch implementation matches the actual request.