github-issues-manager

Files (2)

• SKILL.md
• issue-template.md · templates/

SKILL.md (first lines)

# GitHub Issues Manager

Ensure every unit of work has a trackable GitHub issue with proper labels, acceptance criteria, and relationships.

## Issue Creation Protocol

**Before creating issues, gather context:**
```bash
gh repo view                    # Verify repository
gh milestone list               # Check existing milestones
gh label list                   # Review label taxonomy
```

**For each quantifiable task, create an issue:**
```bash
gh issue create \
  --title "[TYPE] Brief description" \
  --body "$(cat <<EOF
## Description
[What needs to be done]

## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3

## Context
[Why this is needed, related features]

## Technical Notes
[Implementation hints, gotchas]

## Related
- Depends on: #XX
- Blocks: #YY
- Part of: #ZZ
EOF
)" \
  --label "type/[TYPE]" \
  --label "priority/[P0|P1|P2]" \
  --label "area/[AREA]" \
  --milestone "[MILESTONE]"
```

## Issue Types

Labels follow the taxonomy in `rules/git-workflow.md` § Label Taxonomy: every issue carries one `type/*` (`type/feature`, `type/bug`, `type/chore`, `type/refactor`, `type/docs`), one `priority/*` (`priority/P0` blocking, `priority/P1` high, `priority/P2` medium/low), and at least one `area/*`. Run `gh label list` and reuse what exists.

## Batch Issue Creation

When breaking down a feature into multiple issues:

```bash
# Create parent epic/feature issue first
PARENT=$(gh issue create --title "[feat] Feature Name" --body "..." --label "type/epic")

# Create child issues referencing parent
gh issue create --title "[feat] Subtask 1" --body "$(printf 'Part of %s\n\n...' "$PARENT")"
gh issue create --title "[feat] Subtask 2" --body "$(printf 'Part of %s\n\n...' "$PARENT")"
```

## Rules

1. **One issue per deployable unit** - If it can be merged independently, it's one issue
2. **Clear acceptance criteria** - Anyone should verify completion
3. **Link everything** - Issues, PRs, commits reference each other
4. **Update, don't abandon** - If scope changes, update the issue
5. **Close with context** - Note what was done when closing
6. **Create issues BEFORE starting implementation**

## Additional Resources

- For issue creation templates (standard, epic, bug report), see [templates/issue-template.md](templates/issue-template.md)

From roborracle/agent-workflow-kit, MIT.

More from roborracle/agent-workflow-kit