smithery.ai

gh-issues

Create and manage GitHub issues with duplicate detection and hierarchy support.

First seen Mar 16, 2026

Installation

$ npx skills add https://smithery.ai

Summary

  • Create and manage GitHub issues with duplicate detection and hierarchy support.
  • Use when creating issues, filing bugs, tracking tasks, managing sub-issues, or organizing parent/child relationships.
  • Triggers on "create issue", "file bug", "track this", "sub-issue", "parent issue", "break down", "list sub-issues".

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,762 B
  • docs SUMMARY.md 330 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

GitHub Issues Management

Routing

Creating a new issue? → Read [references/creating.md](references/creating.md)

  • Duplicate detection, codebase analysis, solution research
  • Out-of-scope issue tracking during development

Managing issue hierarchy? → Read [references/hierarchy.md](references/hierarchy.md)

  • Create/list/remove sub-issues
  • Check parent issues
  • Decide: new parent vs add to existing

Both? (Creating an issue as a sub-issue):

  1. Follow creating.md workflow to draft and create the issue
  2. Then follow hierarchy.md to link it as a sub-issue

Quick Commands

# Get current repo
gh repo view --json owner,name --jq '"\(.owner.login)/\(.name)"'

# Create issue
gh issue create --title "type(area): description" --body "content"

# View issue
gh issue view <number>

# List issues
gh issue list --state open --limit 20

Title Conventions

Use conventional format:

  • fix(area): description - Bug fixes
  • feat(area): description - New features
  • refactor(area): description - Code improvements
  • docs(area): description - Documentation
  • chore(area): description - Maintenance

Issue Body Template

## Summary
[1-2 sentences]

## Context
[Background, how discovered, why it matters]

## Current Behavior (for bugs)
[What happens now]

## Expected Behavior
[What should happen]

## Additional Context
[Related issues, links, etc.]