Add /gh-notif-triage skill for clearing notification inbox noise#204
Draft
ikuwow wants to merge 1 commit into
Draft
Add /gh-notif-triage skill for clearing notification inbox noise#204ikuwow wants to merge 1 commit into
ikuwow wants to merge 1 commit into
Conversation
Implements the design settled in #186: a Skill that lists the GitHub notification inbox, classifies threads per a reason-based rule table, and marks the noise (ci_activity / subscribed / state_change) as done via DELETE /notifications/threads/<id>. Semi-automatic by default (prints candidates and waits), full-auto with the `auto` argument. Closes #186. Co-authored-by: Claude Opus 4.6 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #186.
Why
The notification inbox accumulates threads that rarely deserve attention (CI results, subscription updates, close / merge notices). Clearing them by hand is toil. The skill encodes the rule-based classification the issue settled on, so the work fits into a single
/gh-notif-triageinvocation.What
claude/skills/gh-notif-triage/SKILL.mdfollows the design from Add /gh-notif-triage Skill: triage GitHub notifications and mark noise as done #186 verbatim. Argument handling: bare invocation lists unread,allincludes already-read,autoskips the approval step.reason → done | keeplives at the top of the skill so the user can edit it inline as preferences change.claude/settings.jsonaddsSkill(gh-notif-triage)andSkill(gh-notif-triage *)toallow.Notes
DELETEstill surfaces anaskprompt because of theBash(gh api * -X *)rule in settings.json; that is acceptable for the initial workflow and matches the issue's call.review_requested/mention/assign) are reachable from other GitHub views.Verification
gh api '/notifications?all=false&per_page=1' --jq '. | length'returns a valid count — the endpoint the skill depends on is reachable from this user.jq . claude/settings.jsonvalidates./gh-notif-triage(live invocation) lists candidates and waits for approval before anyDELETE— deferred to first real use to avoid surfacing a fresh permission prompt mid-batch./gh-notif-triage allwidens the fetch to read+unread./gh-notif-triage autoskips approval.ci_activitynotification confirms it leaves the inbox (gh api '/notifications?all=false') — defer until the first organic triage so a real ci_activity exists to clear.