| name | work-item-handler |
| description | Fetch and manage work items from issue trackers. Use this skill when: - User references an issue number (#42, PROJ-123) - User asks about requirements or acceptance criteria - User needs to understand current task scope |
Work Item Handler
Integrate with issue trackers (GitHub, JIRA, Azure DevOps) for context-aware assistance.
When to Use This Skill
Proactively invoke when user:
- Mentions an issue number
- Asks about requirements or "what needs to be done"
- Needs to fetch/refresh issue details
- Is unclear about task scope
Context Files (Auto-Injected)
- git.yml: Commit and PR format rules (SINGLE SOURCE OF TRUTH)
- git.md: Detailed commit/PR examples
- work-items.yml: Work item lifecycle
- work-items.md: Multi-platform patterns and examples
Read these files for complete guidance. This skill provides quick reference only.
Quick Reference
Fetch Issue (GitHub)
gh issue view <number> --json number,title,body,state,labels
Use /onus:fetch Command
For full fetch with caching:
/onus:fetch 42
Caching
- Location:
~/.claude/onus/work-item-cache.json - Expires: 1 hour
- Refresh:
/onus:fetch <number>
Key Rules
- Don't define commit/PR formats here — that's git.yml's job
- Don't guess issue numbers — verify with user or parse from branch
- Track acceptance criteria — warn before PR if unaddressed
What This Skill Does NOT Do
- Define commit message format (see git.yml/git.md)
- Define PR format (see git.yml/git.md)
- Define work item lifecycle (see work-items.yml)
- Provide detailed fetch examples (see work-items.md, commands/fetch.md)