Triage GitHub notifications and report actions needed.
Fetch, classify, and report on GitHub notifications. The script does the heavy lifting — this skill orchestrates invocation and presents results.
# Report-only (default): show what needs attention, no modifications
python3 scripts/github-notification-triage.py
# Mark informational notifications as read after reporting
python3 scripts/github-notification-triage.py --mark-read
# Save report to ~/.claude/reports/notifications/
python3 scripts/github-notification-triage.py --save
# Cron/scheduled mode: auto-clear noise and save report
python3 scripts/github-notification-triage.py --mark-read --save
Run report-only by default:
python3 scripts/github-notification-triage.py
Display the script output directly to the user. The report classifies notifications into:
If the user responds with any of the following, re-run with --mark-read:
python3 scripts/github-notification-triage.py --mark-read
Confirm how many notifications were marked read after the run completes.
When invoked on a schedule (no interactive user), use both flags to auto-clear and persist the report:
python3 scripts/github-notification-triage.py --mark-read --save
| Code | Meaning |
|---|---|
| 0 | Success |
| 1 | Error (auth failure, API error, script not found) |