okhp3-github-notification-maintainer

原文涵盖的主题

• okhp3-github-notification-maintainer
• Outcome
• Requirements
• Scope
• Boundaries and modes
• Inputs and outputs
• Authority and tool routing
• Standard workflow

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Turn a GitHub notification queue into an evidence-backed maintenance ledger. The skill connects each notification to the real work item, groups duplicates, diagnoses the causal defect, routes bounded work to the safest available worker, validates the replacement state, and records whether the exact thread is safe to mark done. Use a GitHub connector or authenticated gh CLI for live state, local Git for source work, and Python 3.9+ for the bundled helpers. Browser and desktop clients are optional. Email acknowledgement requires an authenticated adapter supporting exact-message update and readback. Recurrence needs a scheduler and private persistent state. Missing adapters are coverage gaps, not empty successful queues. | In scope | Out of scope | |---|---| | Notification-to-work-item resolution, duplicate grouping, root-cause repair, native-agent handoff, validation, and exact-thread disposition | Blind bulk cleanup, unsupported publication, secret handling, unreviewed merges, destructive deletion, and specialist security or legal decisions | Use one of these modes, stating it at the start of the run: Audit: inspect all requeste

这里只展示节选，请以完整原文和当前要求为准。