github-issue-triage
Automated GitHub issue triage with real-time streaming analysis and background task parallelization.
- Launches one independent background task per issue for concurrent analysis, eliminating sequential bottlenecks
- Streams results in real-time as each task completes, providing immediate visibility into critical issues and recommended actions
- Categorizes issues by type (bug, feature, question, invalid) and status (resolved, needs action, can close, needs info) with priority flagging for critical or blocking problems
- Generates a comprehensive final report with actionable summaries, draft responses, and categorized issue lists organized by urgency and next steps
GitHub Issue Triage Specialist (Streaming Architecture)
You are a GitHub issue triage automation agent. Your job is to:
- Fetch EVERY SINGLE ISSUE within time range using EXHAUSTIVE PAGINATION
- LAUNCH 1 BACKGROUND TASK PER ISSUE - Each issue gets its own dedicated agent
- STREAM RESULTS IN REAL-TIME - As each background task completes, immediately report results
- Collect results and generate a FINAL COMPREHENSIVE REPORT at the end
CRITICAL ARCHITECTURE: 1 ISSUE = 1 BACKGROUND TASK
THIS IS NON-NEGOTIABLE
EACH ISSUE MUST BE PROCESSED AS A SEPARATE BACKGROUND TASK
| Aspect | Rule |
|---|---|
| Task Granularity | 1 Issue = Exactly 1 task() call |
More from code-yeongyu/oh-my-opencode
github-triage
Read-only GitHub triage for issues AND PRs. 1 item = 1 background task (category: quick). Analyzes all open items and writes evidence-backed reports to /tmp/{datetime}/. Every claim requires a GitHub permalink as proof. NEVER takes any action on GitHub - no comments, no merges, no closes, no labels. Reports only. Triggers: 'triage', 'triage issues', 'triage PRs', 'github triage'.
802frontend-ui-ux
Designer-turned-developer who crafts stunning UI/UX even without design mockups
255github-pr-triage
Triage GitHub Pull Requests with streaming analysis. CRITICAL: 1 PR = 1 background task. Processes each PR as independent background task with immediate real-time streaming results. Conservative auto-close. Triggers: 'triage PRs', 'analyze PRs', 'PR cleanup'.
96git-master
MUST USE for ANY git operations. Atomic commits, rebase/squash, history search (blame, bisect, log -S). STRONGLY RECOMMENDED: Use with task(category='quick', load_skills=['git-master'], ...) to save context. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.
93work-with-pr
Full PR lifecycle: git worktree → implement → atomic commits → PR creation → verification loop (CI + review-work + Cubic approval) → merge. Keeps iterating until ALL gates pass and PR is merged. Worktree auto-cleanup after merge. Use whenever implementation work needs to land as a PR. Triggers: 'create a PR', 'implement and PR', 'work on this and make a PR', 'implement issue', 'land this as a PR', 'work-with-pr', 'PR workflow', 'implement end to end', even when user just says 'implement X' if the context implies PR delivery.
92pre-publish-review
Nuclear-grade 16-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (5 agents) for holistic review, and 1 oracle for overall release synthesis. Use before EVERY npm publish. Triggers: 'pre-publish review', 'review before publish', 'release review', 'pre-release review', 'ready to publish?', 'can I publish?', 'pre-publish', 'safe to publish', 'publishing review', 'pre-publish check'.
90