mcpField
M
managing-github-issues

managing-github-issues

github.com/hjewkesDevelopment439 installsUpdated 35w ago
Repository

About managing-github-issues

A skill for handling GitHub issues throughout a development session, from finding ready work to closing completed issues. It documents issue creation, label conventions, and links between issues, commits, and pull requests.

Key features

  1. 01Find issues by label or milestone
  2. 02Create issues with structured acceptance criteria
  3. 03Apply a consistent label taxonomy
  4. 04Link commits and pull requests to issues
  5. 05Close issues and check newly unblocked work

Use cases

  1. 01Find high-priority work at the start of a session
  2. 02Create a feature issue with acceptance criteria
  3. 03Reference an issue in a commit or pull request
  4. 04Check for newly available work after closing an issue

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/hjewkes/agent-skills --skill managing-github-issues

After installing, type/managing-github-issuesin Claude Code to confirm it loaded.

Details

From the project README

Managing GitHub Issues

Use this skill when starting a session to find work, creating/triaging issues, or completing work and updating issue status.

Finding Work

Start of session — check what's ready:

gh issue list --label priority:high --label status:ready
gh issue list --label priority:high
gh issue list --milestone "v0.1.0" --state open

Creating Issues

Use structured bodies with Summary + Acceptance Criteria checklist:

gh issue create --title "Add X component" \
  --body "## Summary\n\nBrief description.\n\n## Acceptance Criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2" \
  --label "type:feature,area:components,priority:medium"

Working on Issues

  • Reference #N in commit messages
  • Use Fixes #N in PR descriptions to auto-close

Completing Work

  • Close issues via PR merge (preferred) or gh issue close N
  • After closing, check for newly unblocked work

Label Taxonomy

CategoryLabels
Typetype:feature, type:bug, type:task
Prioritypriority:high (do next), priority:medium (soon), priority:low (backlog)
Areaarea:components, area:tokens, area:infra, area:docs, area:storybook
Statusstatus:ready (can start), status:needs-design (needs decisions)
OSSgood first issue

Comments

Markdown supported