skills.rest
RorySullivan1
RorySullivan1COMMUNITY
Explore all skills by this author →
GitHub

github-issues

Creates, triages, and closes GitHub issues using MCP tools or the gh CLI.

Updated Jul 25, 2026
Search Tags:#github#bug report#backlog#issues#triage#labels#sub-issues
One-click install
npx skills add https://github.com/RorySullivan1/powerapp_taskmaster --skill github-issues-rorysullivan1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/RorySullivan1/powerapp_taskmaster/tree/main/.claude/skills/github-issues
Command: npx skills add https://github.com/RorySullivan1/powerapp_taskmaster --skill github-issues-rorysullivan1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing and managing GitHub issues well is harder than it looks: duplicates fragment discussion, vague bug reports stall maintainers, and fixed issues get left open. This Skill turns issue handling into a disciplined workflow so every issue is actionable, findable, and properly closed. ## Core Features & Use Cases - Duplicate-First Filing: Searches existing issues with search_issues or gh issue list --search before opening anything new, and links near-duplicates instead of splitting the conversation. - Structured Bug Reports and Feature Requests: Produces reports with reproduction steps, expected-vs-actual behavior, environment, and evidence, and honors the repo's .github/ISSUE_TEMPLATE/ forms. - Triage and Breakdown: Applies the repo's existing label taxonomy, sets types/milestones/assignees, and splits epics into independently shippable sub-issues via sub_issue_write. - Use Case: A user reports "the upload retries forever on 503." The Skill searches for duplicates, files a titled bug report with repro steps and logs, labels it bug, and later links the fixing PR with Closes #N so the issue auto-closes on merge. ## Quick Start Ask the assistant to file a GitHub issue for the bug you just found, including reproduction steps and a check for existing duplicates.

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I write a good GitHub bug report?▼

Lead with the symptom as a specific, searchable title, then include steps to reproduce, expected versus actual behavior, environment details, and evidence such as logs or stack traces. One bug per issue keeps it actionable.

How do I avoid filing duplicate GitHub issues?▼

Search existing issues first using search_issues or gh issue list --search with key terms and error text. If a match exists, comment or upvote there instead; link genuine near-duplicates with a reference like "Related to #45".

Should I use GitHub MCP tools or the gh CLI for issue management?▼

Prefer the GitHub MCP tools (issue_write, issue_read, list_issues, search_issues, sub_issue_write) when they are available, since they integrate directly with the assistant. Fall back to the gh CLI when MCP tools are not present.

How do I break a large GitHub epic into sub-issues?▼

Create a parent issue and link children with sub_issue_write, or use a task list like "- [ ] #123" in the body where sub-issues are unavailable. Each child should be independently shippable and understandable without extra context.

When should a GitHub issue be closed manually versus automatically?▼

Prefer automatic closing by putting "Closes #N" in the fixing PR body so the issue closes on merge. Close manually only with a reason and pointer, such as "Fixed in #210" or a won't-fix explanation, and never close silently.

Related Skills

Explore More Software Engineering Skills→
daodaoedudaodaoedu

file-bug-issue

Create a reproducible GitHub issue with reproduction steps and environment details.

Official
Intermediate
wan-huiyanwan-huiyan
3

gh-squash-merge-closes-only-one-issue

Diagnoses and fixes GitHub squash-merge auto-close leaving referenced issues open.

Community
Basic
catu-aicatu-ai
12

issue-triage

Classify and label GitHub issues for the easyharness repository.

Official
Intermediate
russosalvrussosalv
5

spec-to-workitem

Translate NONoise sprint manifest macro tasks into external issue tracker work items.

Community
Advanced