github-notification-triage

To triage GitHub notifications, this Skill classifies inbox items into actionable work like PR review queues and assigned issues, isolating them from informational CI bot noise. It generates a report first so you can review what needs attention before marking items read.

The best way to automate GitHub inbox cleanup is using a scheduled triage flow that identifies informational notifications like bot comments and automated updates. You run it in report-only mode first, then re-run with marking behavior to safely clear the noise.

Yes, you can mark informational GitHub notifications as read without losing track of assigned issues. The Skill produces a safe report separating actionable items like assigned issues from informational noise, only marking items read when you explicitly confirm the cleanup.

You do not need any external dependencies to run the Python-based notification triage report. The Skill operates independently with no listed dependencies, relying only on standard Bash read and write tool access to optionally save results and mark notifications read.

The GitHub notification triage runs in report-only mode before marking anything read to ensure safe reporting first. This approach lets you see what is going on in your inbox, distinguishing actionable PR reviews from CI noise, before any changes are committed.