Review Triage Queue
Create a read-only, local triage queue report from OpenShell GitHub intake.
Install
npx skills add NVIDIA/OpenShell --skill review-triage-queue -g -a claude-code -y- Repository
- NVIDIA/OpenShell20.9k
- Category
- Git and review
- Updated
- 4d ago
- License
- Apache-2.0
- Context cost
- Lightabout 1,383 tokens
- Runs scripts
- No, instructions only
What it does
Create a read-only, local triage queue report from OpenShell GitHub intake. Use to review the triage queue, scan incoming issues and community PRs, check main-branch CI failures, or resume a triage pass.
Review Triage Queue
Create a decision-focused, local Markdown report. Do not write to GitHub.
Local state
Use these ignored local paths under .agents/triage-duty/:
- Checkpoint:
state.local.yml - Reports:
reports/<UTC timestamp>.md - Action records:
actions/<UTC timestamp>.md - Inbox:
inbox.md
Record first-run coverage. Update cursors only after a complete report; partial reads must not skip unread items. Search with overlap and deduplicate source items.
Keep the checkpoint minimal: repository, last successful scan, source and backlog cursors, explicit dispositions, and next triage issue. Action records are authoritative; reconcile the checkpoint from them before proceeding. Reports are immutable. Never store credentials, personal data, private reasons, or vulnerability details; never stage duty files.
Read unchecked inbox entries at the start of every review. Treat them as local follow-up prompts, not as independent evidence or authorization for an external action. When an entry materially informs the review, include it in the report's Local inbox follow-up section. After the dated report is written, mark that entry complete in the inbox with the report filename. Leave entries unchecked when they were not yet actionable or were not considered.
Gather intake
Follow Label Discovery, retrieving all pages of current label definitions. Identify the triage queue by its description. Read all pages of each source:
