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 describing pull requests on GitHub.
The repository uses GitHub if git remote -v shows github.com URLs.
gh pr view <number> --repo <org>/<repo> --json title,body,baseRefName,headRefName,commits
gh pr diff <number> --repo <org>/<repo>Check in this order:
.github/PULL_REQUEST_TEMPLATE.md.github/pull_request_template.mdPULL_REQUEST_TEMPLATE.mdpull_request_template.md.github/PULL_REQUEST_TEMPLATE/ directory (use first .md file)gh issue list --repo <org>/<repo> --state open --search "<terms>" --limit 5Write the description to a temp file named with the PR number to avoid collisions, then update both fields in a single call:
gh pr edit <number> --repo <org>/<repo> \
--title "<conventional-commits-title>" \
--body-file /tmp/pr-description-<number>.mdTo update only the title (e.g., when the existing description is fine):
gh pr edit <number> --repo <org>/<repo> --title "<conventional-commits-title>"