issue

Generate an actionable implementation plan from a GitHub issue's metadata and linked PRs.

29|1|Updated Jul 18, 2015
One-click install
npx skills add https://github.com/joshmanders/dotfiles --skill issue-joshmanders
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/joshmanders/dotfiles/tree/main/claude/skills/issue
Command: npx skills add https://github.com/joshmanders/dotfiles --skill issue-joshmanders

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and organize work around a GitHub issue by pulling issue details and generating an actionable implementation plan.

Core Features & Use Cases

  • Parse an issue reference to identify repo and issue number.
  • Fetch issue details, including the description, comments, acceptance criteria, and linked PRs.
  • Draft and track an actionable implementation plan that can be executed after plan approval.

Quick Start

Provide an issue reference to begin planning the work for that GitHub issue.

Frequently Asked Questions about issue

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

FAQPage Schema
How do I generate an implementation plan from a GitHub issue?

To generate an implementation plan from a GitHub issue, you provide the issue reference. The tool parses the reference, fetches issue details via GitHub API patterns, and drafts an actionable plan.

Can I use this to plan work for individual issues across different repositories?

Yes, you can plan work for individual issues across repositories. The tool parses the issue reference to identify the specific repository and issue number before fetching the data.

What GitHub issue details are included when creating an actionable plan?

When creating an actionable plan, the tool extracts issue details including the description, comments, acceptance criteria, and linked PRs to form a comprehensive implementation workflow.

What's the best way to organize work around a GitHub issue before coding?

The best way to organize work around a GitHub issue is pulling issue details and generating an end-to-end implementation plan that can be tracked and executed after plan approval.

Do I need to manually link pull requests when planning a GitHub issue workflow?

No, you do not need to manually link pull requests. The planning workflow automatically fetches linked PRs along with descriptions, comments, and acceptance criteria to derive the executable plan.