# Gh Issues

> 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".

- Skill: `ainergiz/gh-issues` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add ainergiz/gh-issues`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ainergiz/gh-issues/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ainergiz (https://skillmd.com/u/ainergiz)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ainergiz/gh-issues

---


# 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

```bash
# 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

```markdown
## 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.]
```