skills.rest
matsen
matsenCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

issue-next

Extract next-action signals from GitHub PRs and file follow-up issues.

29|4|Updated Jan 12, 2026
Search Tags:#automation#workflow#template#planning#github#issue
One-click install
npx skills add https://github.com/matsen/bipartite --skill issue-next
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-next
Source: https://github.com/matsen/bipartite/tree/main/skills/issue-next
Command: npx skills add https://github.com/matsen/bipartite --skill issue-next

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft a follow-up GitHub issue from PR decisions, ensuring accountability and traceability across teams.

Core Features & Use Cases

  • Automatically extract explicit next-steps and unresolved decisions from PR bodies and reviews.
  • Generate a well-structured issue file that follows Matsengrp standards and links related issues and EPICs.
  • Validate the drafted issue with /issue-check before submission to reduce rework.

Quick Start

Run /issue-next with a PR URL or number to draft and file the issue.

Frequently Asked Questions about issue-next

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

FAQPage Schema
How do I create a follow-up GitHub issue from a pull request decision?▼

To create a follow-up GitHub issue from a PR decision, you can run the /issue-next workflow with a PR URL or number to extract unresolved decisions and automatically file the structured issue.

How do I automatically extract unresolved decisions from PR reviews?▼

Automatically extracting unresolved decisions from PR reviews involves reading the PR body and comments to identify next-action signals, which this workflow processes to generate the most impactful next step.

Can I draft GitHub issues across multiple repositories from PR comments?▼

Yes, you can draft GitHub issues across multiple repositories by applying the workflow to PRs, reviews, and decision notes across repositories to generate structured follow-up issues.

What is the best way to ensure accountability for next-action items discussed in GitHub pull requests?▼

The best way to ensure accountability for next-action items in pull requests is to draft a follow-up GitHub issue that links related issues and EPICs, ensuring traceability across teams.

Does filing a follow-up GitHub issue from a PR require validation before submission?▼

Filing a follow-up GitHub issue from a PR requires validation with the /issue-check workflow before submission to ensure the drafted issue meets standards and reduce rework.

Why should I automate issue creation from pull request notes instead of manual entry?▼

Automating issue creation from pull request notes extracts explicit next-steps and unresolved decisions directly from PR bodies, reducing manual entry errors and ensuring well-structured issue files.

Related Skills

Explore More Software Engineering Skills→
mvillmowmvillmow
18

gh-get-review-comments

Retrieve GitHub pull request review comments via the GitHub API.

Community
Basic
3D-Stories3D-Stories
2

rawgentic:create-issue

Orchestrate a 9-step workflow to create validated GitHub issues.

Official
Advanced
CERTCCCERTCC
21

create-epic

Create GitHub Epics with standardized issue types and labels.

Official
Intermediate
Albarracin-sgAlbarracin-sg

pr-review

Fetch GitHub PR metadata and diffs to categorize issues and draft comments.

Community
Intermediate