comet-github

Describe the request by intent, such as reviewing a PR, triaging an issue, diagnosing CI, or implementing a fix. The router maps each intent to a dedicated sub-skill and returns the routing decision, supporting evidence, and the next safe action.

It covers five flows: PR review, issue triage to confirm whether a report is a real bug, converting local ideas into issues, CI failure diagnosis, and implementing fixes based on an issue. Mixed requests are split into read-only diagnosis first, then a handoff recommendation.

No. The maintainer contract is read-only by default. Commenting, changing labels, closing issues, creating issues, committing, pushing, or creating PRs all require explicit user authorization, with the exact target and resulting changes stated beforehand.

Copied comments, old CI results, review bot summaries, and remembered commit SHAs can be stale. The contract requires refreshing the current branch, head/base, and CI status so conclusions rest on live evidence rather than outdated clues.

It only routes and coordinates; actual review, triage, or fixes happen in the dedicated sub-skills. It never crosses silently from analysis into code changes or GitHub writes, and it reports uncertainty levels such as confirmed, likely, insufficient evidence, or unverified.