skills.rest
DRMacIver
DRMacIverCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Working on GitHub Issues

Guide GitHub issue triage, acceptance criteria, and referencing commits.

18|Updated Jan 19, 2026
Search Tags:#workflow#github#issues#triage#acceptance-criteria#commit-messaging
One-click install
npx skills add https://github.com/DRMacIver/claude-reliability --skill working-on-github-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Working on GitHub Issues
Source: https://github.com/DRMacIver/claude-reliability/tree/main/skills/github-issues
Command: npx skills add https://github.com/DRMacIver/claude-reliability --skill working-on-github-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps users understand GitHub issues, define precise acceptance criteria, and ensure that commits reference the relevant issues, reducing miscommunication and scope creep.

Core Features & Use Cases

  • Read issue bodies and all comments to capture full context.
  • Check related issues and linked PRs to avoid duplication and misalignment.
  • Define clear acceptance criteria before implementing changes.
  • Guide commit practices that reference issue numbers (e.g., "Closes #123") to ensure traceability.
  • Provide a structured workflow for triaging, planning, and delivering features via GitHub issues.

Quick Start

Read the full issue description and comments, then document acceptance criteria and outline your commit plan with proper issue references.

Frequently Asked Questions about Working on GitHub Issues

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

FAQPage Schema
How do I define acceptance criteria for GitHub issues before implementing changes?▼

Defining acceptance criteria for GitHub issues involves reading the issue body and all comments to capture full context, then structuring precise requirements before implementation. This approach reduces miscommunication and scope creep during feature planning and bug reproduction.

What's the best way to triage GitHub issues and check for related duplicated work?▼

Triage GitHub issues by reading the full issue description and comments to capture context, then checking related issues and linked pull requests. This prevents duplication and misalignment across workflows before you start planning feature delivery.

How do I format commit messages to reference GitHub issues and ensure traceability?▼

Format commit messages to reference GitHub issues by including directives like "Closes #123" in your commit text. This practice ensures traceability between your implemented changes and the original GitHub issue during feature delivery.

Can I use this workflow for planning features and reproducing bugs on GitHub?▼

Yes, this workflow applies when triaging issues, reproducing bugs, planning features, and documenting acceptance criteria across workflows using GitHub issues. It enforces reading issue bodies and comments to capture full context before implementation.

Why should I read all comments on a GitHub issue before starting implementation?▼

Reading all comments on a GitHub issue captures full context and identifies related issues or linked PRs. This prevents misalignment and scope creep by ensuring your acceptance criteria and subsequent commits match the actual project requirements.

Related Skills

Explore More Software Engineering Skills→
udecodeudecode
1.2k

reviewing-pr

Automate GitHub pull request reviews with severity-rated feedback.

Official
Intermediate
markus41markus41
18

jira:review

Review linked commits and pull requests for a Jira issue against acceptance criteria.

Community
Intermediate
kamp-uskamp-us
25

ship-it

Automate squash merging of verified Pull Requests with green CI status.

Official
Advanced
henrycashe26henrycashe26

to-issues

Break project plans and PRDs into vertical slice issues with acceptance criteria.

Community
Intermediate