Agent skill
pull-requests
Guide for creating, updating, and following up on pull requests in the Coder repository. Use when asked to open a PR, update a PR, rewrite a PR description, or follow up on CI/check failures.
Install this agent skill to your Project
npx add-skill https://github.com/coder/coder/tree/main/.agents/skills/pull-requests
SKILL.md
Pull Request Skill
When to Use This Skill
Use this skill when asked to:
- Create a pull request for the current branch.
- Update an existing PR branch or description.
- Rewrite a PR body.
- Follow up on CI or check failures for an existing PR.
References
Use the canonical docs for shared conventions and validation guidance:
- PR title and description conventions:
.claude/docs/PR_STYLE_GUIDE.md - Local validation commands and git hooks:
AGENTS.md(Essential Commands and Git Hooks sections)
Lifecycle Rules
-
Check for an existing PR before creating a new one:
bashgh pr list --head "$(git branch --show-current)" --author @me --json number --jq '.[0].number // empty'If that returns a number, update that PR. If it returns empty output, create a new one.
-
Check you are not on main. If the current branch is
mainormaster, create a feature branch before doing PR work. -
Default to draft. Use
gh pr create --draftunless the user explicitly asks for ready-for-review. -
Keep description aligned with the full diff. Re-read the diff against the base branch before writing or updating the title and body. Describe the entire PR diff, not just the last commit.
-
Never auto-merge. Do not merge or mark ready for review unless the user explicitly asks.
-
Never push to main or master.
CI / Checks Follow-up
Always watch CI checks after pushing. Do not push and walk away.
After pushing:
- Monitor CI with
gh pr checks <PR_NUMBER> --watch. - Use
gh pr view <PR_NUMBER> --json statusCheckRollupfor programmatic check status.
If checks fail:
- Find the failed run ID from the
gh pr checksoutput. - Read the logs with
gh run view <run-id> --log-failed. - Fix the problem locally.
- Run
make pre-commit. - Push the fix.
What Not to Do
- Do not reference or call helper scripts that do not exist in this repository.
- Do not auto-merge or mark ready for review without explicit user request.
- Do not push to
origin/mainororigin/master. - Do not skip local validation before pushing.
- Do not fabricate or embellish PR descriptions.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
refine-plan
Iteratively refine development plans using TDD methodology. Ensures plans are clear, actionable, and include red-green-refactor cycles with proper test coverage.
deep-review
Multi-reviewer code review. Spawns domain-specific reviewers in parallel, cross-checks findings, posts a single structured GitHub review.
doc-check
Checks if code changes require documentation updates
code-review
Reviews code changes for bugs, security issues, and quality problems
mobile-dev-server-sandbox
Connects Mux mobile (Expo web/native) to an isolated dev-server sandbox with deterministic port setup, backend pairing, and Chrome MCP interaction. Use when implementing or validating mobile features against a sandboxed Mux backend.
dev-desktop-sandbox
Run isolated mux desktop (Electron) instances (temp MUX_ROOT + free ports)
Didn't find tool you were looking for?