Coding-agent skills for pull-request work and orchestration: an adversarial multi-pass PR reviewer, PR description and title writing, answering review comments, CI failure triage and PR nursing, a DAG orchestrator that delegates to cheaper subagents, and file-channel coordination between agents. Supports GitHub and GitLab.
95%
Does it follow best practices?
Impact
98%
1.88xAverage score across 10 eval scenarios
Low
Low-risk findings worth noting
Platform-specific commands for responding to PR review comments on GitHub.
The repository uses GitHub if git remote -v shows github.com URLs.
gh api repos/<org>/<repo>/pulls/<number>/comments \
--jq '[.[] | {id, path, line, body, user: .user.login, html_url, in_reply_to_id}]'For PR-level (issue) comments:
gh api repos/<org>/<repo>/issues/<number>/comments \
--jq '[.[] | {id, body, user: .user.login, html_url}]'The html_url field is the permalink to the comment — use it when replying to link back to the original comment.
gh pr diff <number> --repo <org>/<repo>gh api repos/<org>/<repo>/pulls/<number>/comments \
--method POST \
--field body="<reply>" \
--field in_reply_to=<comment-id>gh api repos/<org>/<repo>/issues/<number>/comments \
--method POST \
--field body="<reply>"GitHub does not support resolving individual comments via the API directly. Threads are resolved through the web UI or when a review is submitted. After pushing fixes, the reviewer typically resolves their own threads.