Github comment triage
Skill charlieviettq/awesome-agent-skill/.cursor/skills/core-workflow/github-comment-triage
Curated skill pack for LLM agents in engineer and science workflow (Cursor & Claude ready).
npx -y skills add charlieviettq/awesome-agent-skill --skill github-comment-triageAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 22 stars22 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Triage and address GitHub PR review comments systematically—classify, respond, fix or defer with rationale. Use when a PR has review feedback, requested changes, or unresolved threads. Triggers: "PR comments", "review feedback", "address comments", "requested changes".
SKILL.md
1.4 KB, 259 tokens by cl100k_base, as published. Nobody here has run it
GitHub comment triage
Workflow
- Collect all open review threads and inline comments (not just summary).
- Classify each item:
- Must fix — correctness, security, contract break, CI
- Should fix — clarity, maintainability, agreed convention
- Discuss — ambiguous or product decision
- Defer — out of scope; needs follow-up issue
- Order must-fix first, then should-fix, then discuss.
- Implement with minimal scoped changes; one logical commit per theme when possible.
- Reply on each thread: what changed, where, or why deferred (link issue if deferred).
- Re-verify tests/lint before requesting re-review.
Response patterns
Fixed in abc123 — [brief what changed]
Deferred: tracked in #NNN — [reason and scope boundary]
Anti-patterns
- Bulk "fixed" without pointing to commits or files.
- Ignoring nitpicks that hide real bugs.
- Expanding scope to unrelated refactors during comment sweep.
Output
Checklist table: comment | action | status | note.