From onus
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
npx claudepluginhub flexion/claude-domestique --plugin onusThis skill uses the workspace's default tool permissions.
Integrate with issue trackers (GitHub, JIRA, Azure DevOps) for context-aware assistance.
Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.
Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.
Integrate with issue trackers (GitHub, JIRA, Azure DevOps) for context-aware assistance.
Proactively invoke when user:
Read these files for complete guidance. This skill provides quick reference only.
Before proceeding, check for project-level rules that may override onus defaults:
Scan for project rules
find .claude/rules -name '*.md' 2>/dev/null
If files found, read any that relate to work items, issues, or the specific platform (match by filename, e.g. work-items.md, jira.md, by frontmatter domain: / type: fields, or by extends: onus/work-items.md)
Check for companion context — if a rule file's frontmatter contains a companion: field, also read that file from .claude/context/
State the source
Apply precedence: project rules override plugin defaults
gh issue view <number> --json number,title,body,state,labels
For full fetch with caching:
/onus:fetch 42
~/.claude/onus/work-item-cache.json/onus:fetch <number>