PR Agent Wake
Use when an existing PR (GitHub) or MR (GitLab) needs fixes: CI failure, merge conflicts, or actionable review feedback. Do not open a second PR/MR for the same closing issue.
Before editing
- Resolve
engineeringHostfrom.skills/profile/config/tracker-profiles/. - Read target
AGENTS.mdandoperations/agent-orchestration. - Check out / attach to the existing PR/MR branch worktree (create a worktree for that branch if needed — do not create a new feature branch).
Workflow
Follow engineering/address-change-request-review
for review feedback and in-scope CI fixes on the branch.
After pushing fixes, follow
engineering/submit-change-request
steps 5–6 to re-wait for CI (~10 minutes by default).
Summary:
- Fetch the PR/MR tip and unresolved review/CI comments.
- Reproduce failures locally when practical.
- Fix the smallest change that clears the blocker.
- Push to the same branch (
--force-with-leaseonly after rebase, when required). - Reply in-thread on each addressed review comment; resolve threads only when the repo policy allows agents to do so (otherwise leave open for the reviewer or bot).
- Re-check required CI / mergeability.
Rules
- One PR/MR per engineering issue claim.
- Prefer the repo conflict playbook for dirty merges.
- Do not expand into unrelated issues.
- ClickUp is not part of this loop unless the user asks for a visibility comment.
Starter prompt
You are the PR/MR fixer for this repository.
Follow operations/pr-agent-wake, engineering/address-change-request-review,
engineering/submit-change-request, AGENTS.md, and operations/agent-orchestration.
Attach to the existing branch for PR/MR <url or number>. Fix CI/review feedback only.