skills.rest
jlaws
jlawsCOMMUNITY
Explore all skills by this author →
GitHub

github-issue-resolution

Triage GitHub issues and generate pull requests with root-cause analysis.

2|Updated Jan 3, 2026
Search Tags:#workflow#github#branching#root-cause-analysis#pull-request#bug-fix#issue-triage
One-click install
npx skills add https://github.com/jlaws/dotfiles --skill github-issue-resolution
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issue-resolution
Source: https://github.com/jlaws/dotfiles/tree/main/.agents/skills/workflow/github-issue-resolution
Command: npx skills add https://github.com/jlaws/dotfiles --skill github-issue-resolution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic methodology for investigating, triaging, implementing, and resolving GitHub issues, covering the full issue-to-PR lifecycle, with clear guardrails to avoid scope creep and miscommunication.

Core Features & Use Cases

  • Issue Investigation: Retrieve issue details, comments, labels, assignees, and milestones to enable precise triage and planning.
  • Root Cause Analysis and Branching: Apply reasoning techniques (bisect, blame) and propose robust branching strategies for timely, safe fixes.
  • PR Creation and Post-Implementation: Prepare PRs with clear summaries, checks, and post-merge follow-ups suitable for bug fixes and feature work.

Quick Start

Triages a GitHub issue, creates a feature or bug-fix branch, and opens a PR with a concise summary.

Frequently Asked Questions about github-issue-resolution

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

FAQPage Schema
How do I systematically triage and resolve GitHub issues from start to finish?▼

To systematically triage and resolve GitHub issues, you document investigation steps, apply root-cause analysis, implement a fix on a dedicated branch, and open a pull request. This handles the full issue-to-PR lifecycle including post-implementation checks.

What is the best way to apply root-cause analysis when fixing a GitHub bug?▼

Root-cause analysis for a GitHub bug involves applying reasoning techniques like bisect and blame to retrieve issue details and comments. This precise triage enables robust branch strategies for safe, timely fixes during the pull request workflow.

How do I create a pull request for a bug fix without causing scope creep?▼

Creating a pull request for a bug fix without scope creep requires clear guardrails during issue investigation. By systematically documenting triage steps and root-cause analysis, the PR summary stays concise and avoids miscommunication.

Can I use this workflow for feature implementation from existing GitHub issues?▼

Yes, this workflow applies to feature implementation from existing GitHub issues alongside bug triage. It manages the full lifecycle from issue creation to PR merge by retrieving details, proposing branching strategies, and preparing post-merge follow-ups.

Does issue triage work for managing milestones and labels before branching?▼

Issue triage retrieves milestones, labels, and assignees before branching to enable precise planning. Documenting these investigation steps ensures the root-cause analysis and subsequent pull request workflow align with the project's lifecycle management.

Related Skills

Explore More Software Engineering Skills→
tomholfordtomholford
6

view-issue

... (see below)

Community
Intermediate
p-o-ke-naep-o-ke-nae

github-flow

Guide GitHub Flow branching, commits, testing, pull requests, and squash merges.

Community
Intermediate
BradliebsBradliebs

investigate

Diagnose software failures through a four-phase root-cause investigation workflow.

Community
Advanced
EtaCassiopeiaEtaCassiopeia

ship-issues

Orchestrate GitHub issue lifecycle from triage to merge.

Community
Advanced