From triage
Weekly review of your Triage Board — work through stale Tier 1 and Tier 2 cards, check Jira for assigned tickets, and clean up the backlog. Run on Fridays or at the start of the week.
How this command is triggered — by the user, by Claude, or both
Slash command
/triage:reviewThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /review Weekly board sweep: surface overdue cards, prompt decisions on stale items, and pull Jira tickets assigned to you so nothing slips through. --- ## Steps ### 0. Read workspace config Read `skills/triage/references/workspace-config.md` to get board backend, board ID/collection ID, and board URL. --- ### 1. Load the board Use `notion-search` with `data_source_url` set to the configured **Database collection ID** (`collection://...`) and `page_size: 25`, paginating until all pages are retrieved. Do NOT use `notion-fetch` on the database ID — that returns schema only. Group re...
Weekly board sweep: surface overdue cards, prompt decisions on stale items, and pull Jira tickets assigned to you so nothing slips through.
Read skills/triage/references/workspace-config.md to get board backend, board ID/collection ID, and board URL.
Use notion-search with data_source_url set to the configured Database collection ID (collection://...) and page_size: 25, paginating until all pages are retrieved. Do NOT use notion-fetch on the database ID — that returns schema only.
Group results by Status. Build:
Triaged at date more than 3 days ago (overdue — no reply sent)Triaged at date more than 5 days agoCall searchJiraIssuesUsingJql with:
assignee = currentUser() AND statusCategory != Done ORDER BY updated DESC
Request fields: summary, status, priority, updated, assignee, url.
For each ticket, check whether a card already exists on the board (match by Jira ticket URL in the Link field). If no card exists, flag it as a potential gap.
Bucket the results:
Report after fetching: "Found [N] Jira tickets assigned to you — [N] in progress, [N] to do, [N] blocked."
For each stale Tier 1 card (overdue, no reply sent):
AskUserQuestion: "[Card name] has been in Tier 1 for [N] days. What would you like to do?"
Options: Draft reply now / Snooze 3 days / Snooze 1 week / Mark Done / Dismiss (move to Backlog)
For each stale Tier 2 card (5+ days, no action):
AskUserQuestion: "[Card name] — reviewed this week?"
Options: Yes, mark Done / Still relevant — keep / Snooze 1 week / Dismiss
For each Jira gap (assigned ticket with no board card):
AskUserQuestion: "[Ticket ID] [Title] — no board card exists. Add one?"
Options: Add as Tier 1 / Add as Tier 2 / Add as Soon / Skip
If adding a card, create it via notion-create-pages using the Jira ticket URL as the Link and today's date as Triaged at.
Process choices:
/triage step 8Backlog, set Due date = today + N daysDoneBacklog, clear Due dateCall list_events for the past 7 days (from last Monday to today). Filter to events where you are an attendee (not just organiser). Exclude all-day events and declined events.
Compute:
Format as a compact summary:
📅 Meetings this week
[N] meetings — [Xh Ym] total
[N] recurring · [N] one-off
Busiest day: [day] ([Xh])
Focus blocks (90m+): [N]
1:1s: [N]
If Google Calendar is not connected, skip this section silently.
🔍 Weekly review — [date]
Jira: [N] tickets assigned ([N] in progress, [N] to do, [N] blocked)
Board gaps: [N] Jira tickets with no triage card
Board sweep:
- [N] stale Tier 1 cards resolved
- [N] stale Tier 2 cards resolved
- [N] cards snoozed
- [N] cards kept
📅 Meetings this week
[meeting summary from step 4]
[Open Triage Board]([BOARD_URL])
Remind: "Run /triage to pick up anything new, or /standup to generate your standup summary."
npx claudepluginhub matthewweaver/claude-triage/reviewReviews staged changes or recent commits across five axes—correctness, readability, architecture, security, performance—producing categorized findings with file:line references and fixes.
/reviewRuns Codex code review on local git state (working tree or vs base branch). Supports --wait/--background, --base <ref>, --scope auto|working-tree|branch.
/reviewInvokes multiple external AI CLIs (Gemini, Claude, Codex, etc.) to independently review a phase plan and produces a structured REVIEWS.md with per-reviewer feedback.
/reviewRuns an enhanced multi-LLM PR review with inline comments, checking availability of local and API-based providers for cross-model escalation.
/reviewReviews HTML file for design anti-patterns, principles violations, and accessibility issues. Generates markdown report with status tables and recommendations.
/reviewReviews specified code scope via four specialists (quality, security, performance, architecture), producing summary, detailed findings, refactoring suggestions, prioritized action plan.