kit-triage-comments
Skill6 starsChanged 27 days agoMITView on GitHub
Triage PR review comments — choose batch (collect/classify/approve as a set) or one-by-one walkthrough with the user before fixing. Use after review feedback lands.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- rules/AGENTS.mdAGENTS.md
- kit-audit-metricsSkill
- kit-audit-skillsSkill
- kit-capture-lessonSkill
- kit-challenge-designSkill
- kit-check-blastSkill
- kit-create-prSkill
- kit-debate-decision-treeSkill
- kit-debug-prodSkill
- kit-decisionsSkill
- kit-evolveSkill
- kit-explainSkill
- kit-learn-repoSkill
- kit-minimizeSkill
- kit-optimize-contextSkill
- kit-planSkill
- kit-proveSkill
- kit-reviewSkill
- kit-strip-diffSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Not a full PR code review (kit-review)
- Distinctive: line 14
Not silent auto-fix — triage first unless the user says “fix as we go” in walkthrough mode
- Distinctive: line 21
If mode omitted → ask once: batch or walkthrough
- Distinctive: line 59
Recommendation: Must Fix · Should Fix · Optional · Skip
- Very specific: line 92
After confirm, post a short summary (Fixed / Skipped with reasons) via gh pr comment using --body-file -.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Triage Comments
Triage review comments, then fix only what was approved.
What this is NOT
- Not a full PR code review (
kit-review) - Not silent auto-fix — triage first unless the user says “fix as we go” in walkthrough mode
Input
kit-triage-comments [PR_URL_OR_NUMBER] [batch|walkthrough] (all optional)
- Full URL or number, or no input → auto-detect PR from current branch
- If mode omitted → ask once: batch or walkthrough
| Mode | Pace | Best when |
| batch | Full list → approve as a set | Speed / high trust |
| walkthrough | One comment → wait | Decide with the human |
Shared: collect & classify
1. Resolve PR
PR_NUM=$(gh pr view --json number --jq '.number')
OWNER=$(gh pr view --json headRepositoryOwner --jq '.headRepositoryOwner.login')
REPO_NAME=$(gh pr view --json headRepository --jq '.headRepository.name')
REPO="$OWNER/$REPO_NAME"2. Extract all comment types
# A. General PR discussion
gh api repos/$REPO/issues/$PR_NUM/comments
# B. Line-specific review comments
gh api repos/$REPO/pulls/$PR_NUM/comments
# C. Review submissions
gh api repos/$REPO/pulls/$PR_NUM/reviews3. Drop resolved / outdated threads
gh api graphql -f query='query { repository(owner: "'$OWNER'", name: "'$REPO_NAME'") { pullRequest(number: '$PR_NUM') { reviewThreads(first: 100) { nodes { id isResolved isOutdated comments(first: 10) { nodes { id body author { login } }}}}}}}'Skip isResolved or isOutdated.
4. Classify each remaining comment
Severity: Critical · Important · Minor · Noise
Recommendation: Must Fix · Should Fix · Optional · Skip
Guidelines:
- Human comments rank higher than bots
- Bot “Critical” → treat as Important until verified
- “Will this break production?” → Critical
- Preference-only → Minor/Noise
Mode: batch
Present a structured list grouped by severity. For each item include: #, severity, recommendation, author, file:line, quoted comment, proposed solution, short reasoning.
Then ask:
Which should I fix? Reply with numbers (
1, 3), ranges (1-5), severity (all critical),all(Must Fix + Should Fix), ornone.
Mode: walkthrough
- Present only the next comment (quote/paraphrase + link).
- Propose severity + one-line action (fix / reply / defer / disagree).
- Wait for the user’s decision; record it.
- Continue until done.
- Apply approved fixes as a small batch (or fix-as-you-go if they asked).
Rules: no silent fixes during triage; deferred needs a reason.
After approval (both modes)
- Implement only approved fixes; follow repo standards; lint.
- Resolve addressed threads when appropriate:
gh api graphql -f query='mutation { resolveReviewThread(input: {threadId: "<ID>"}) { thread { isResolved }}}'- Pause — ask the user to commit/push and confirm before posting on the PR.
- After confirm, post a short summary (
Fixed/Skippedwith reasons) viagh pr commentusing--body-file -.
Output
Fixed X/Y approved comments | Lint clean | PR updated (when summary posted)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

