Use this Skill as the explicit entry point for Comet GitHub work. Before routing, first readshared maintainer contract。
Route by intent
- "Review PR / look at this PR" →
comet-github-pr-review - "Check whether this Issue holds up / is it a bug" →
comet-github-issue-triage - "File this local idea as an Issue" →
comet-github-idea-to-issue - "CI has an error / which job failed" →
comet-github-ci-triage - "Fix it according to this Issue" →
comet-github-issue-fix
If the request includes both review and fix, first complete the read-only diagnosis, then state which workflow should be suggested for handoff. Do not silently cross from the analysis stage into code modification or GitHub write operations.
Shared routing rules
- Confirm the repository, Issue/PR number or URL, current local branch, and the level of action requested by the user.
- Refresh the live GitHub state before relying on copied comments, old CI results, or remembered SHAs.
- Report evidence, diagnosis, suggested actions, and completed actions separately.
- Explicitly report uncertainty: confirmed, possibly holds up, insufficient evidence, blocked, or unverified.
- Read-only by default. Commenting, changing labels, closing Issues, creating Issues, committing, pushing, or creating PRs all require explicit authorization.
Handoff output
Return a brief routing decision, the selected Skill, the evidence supporting that route, and the next safe action. Preserve the scope specified by the user, and do not treat generated drafts as changes already published to GitHub.