github-notification-cleanup

To filter GitHub notifications for pull requests needing your review, this skill identifies open PRs where you are a reviewer and marks all other notifications as DONE using GraphQL mutations, ensuring only actionable PRs remain visible in your inbox.

You can bulk archive GitHub notifications across multiple repositories while preserving specific PR alerts by using this skill to mark non-critical notifications as DONE, while safeguards prevent the loss of PRs requiring your review.

Yes, you need the gh CLI to automate cleaning up GitHub notification inboxes, as this skill requires gh CLI access to execute GraphQL mutations that mark notifications as DONE or UNREAD.

The best way to manage a cluttered multi-repo GitHub notification inbox is to automate filtering, archiving non-critical alerts as DONE while retaining open PRs where you are a reviewer to reduce distraction and maintain focus.

Yes, you can restore GitHub notifications archived by mistake because the skill includes functionality to selectively restore inbox items by marking them UNREAD as needed after the bulk archive process.

A limitation of automating GitHub notification cleanup with GraphQL is that it requires gh CLI access and careful configuration, although built-in safeguards exist to prevent the loss of keeper PRs during the bulk archiving process.