GitHub: notification triage, profile rule extraction.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
GitHub notification triage and issue/PR queue classification.
| Request | Mode |
|---|---|
| Notifications, inbox, cleanup | Notification Triage |
| Issue or PR queue, review items | Queue Triage |
Fetch, classify, and report GitHub notifications via the triage script.
# Report-only (default)
python3 scripts/github-notification-triage.py
# Mark informational notifications as read
python3 scripts/github-notification-triage.py --mark-read
# Save report to ~/.claude/reports/notifications/
python3 scripts/github-notification-triage.py --save
# Cron/scheduled: auto-clear noise and save
python3 scripts/github-notification-triage.py --mark-read --save
python3 scripts/github-notification-triage.py.--mark-read. Confirm how many
were marked read.Scheduled (no interactive user): run with --mark-read --save.
Exit codes: 0 = success, 1 = error (auth, API, script not found).
When triaging a queue of issues or PRs (not just notifications), produce one card per item.
Open each card with the item's full GitHub URL on its own line, then these fields in order:
| Field | Content |
|---|---|
| What | One sentence: what the issue/PR asks or changes. |
| Why | Motivation or problem it addresses. |
| Author trust | Maintainer, known contributor, first-timer, or bot. Cite prior merged PRs. |
| Fit | Match to project scope and conventions. |
| Risk | Blast radius: files touched, API/behavior changes, security or data paths. |
| Proof state | CI status, tests added, repro steps, screenshots. "Unverified" when none. |
| Blocker | Single thing stopping progress, or "None". |
| Next action | One concrete step with named actor. Label Autonomous or Needs-owner. |
Example:
https://github.com/owner/repo/pull/123
What: Adds retry with backoff to the webhook sender.
Why: Webhooks drop on transient 5xx from receivers.
Author trust: Known contributor, 4 merged PRs.
Fit: Matches existing client retry pattern in net/client.go.
Risk: Low — one module, behavior gated behind config flag.
Proof state: CI green; unit tests cover backoff schedule.
Blocker: None.
Next action: Autonomous — review and merge.
When in doubt, label Needs-owner and state the decision the owner must make.
Before any local work on an item (checkout, tests, repro):
git status --short.<repo>" and continue triaging from API data only.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Manage multiple Claude Code accounts: add, list, check, launch, and install shell aliases for 10+ isolated CLAUDE_CONFIG_DIR profiles.
The English summary is being prepared. Showing the original description.
Improve architecture across modules by deepening interfaces.
The English summary is being prepared. Showing the original description.
Assessment: read-only inspection, codebase overview, value analysis, health checks, ADR consultation, decision analysis, multi-perspective critique.
The English summary is being prepared. Showing the original description.
Background memory consolidation — overnight review, merge, and injection payload for memory files.
The English summary is being prepared. Showing the original description.
Jev-driven browser automation: Jev picks operations, programs execute, a text model writes field values only when Jev cannot pick one from the goal.
The English summary is being prepared. Showing the original description.
Write, compose, integrate, and improve programs that call Jev, TypeSafe's System One judgment model.
The English summary is being prepared. Showing the original description.