GitHub Issues Management

Routing

Creating a new issue? → Read references/creating.md

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

Managing issue hierarchy? → Read 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.]