PR

Prepare the code host's change request or review equivalent so a reviewer can quickly understand the intent, important files, and risk, while the code's behavior stays unchanged.

Read docs/agents/workflow.md and docs/agents/code-host.md, and docs/agents/issue-tracker.md for linked work items. In a repo configured before code-host.md existed, use any code-host operations recorded in issue-tracker.md until setup is refreshed. Follow the configured delivery and closure policy when creating or updating the request, including its actor, readiness, and closing-reference rules. Check existing closing references as well as new ones against ticket and parent-spec policy. When the code host and tracker differ, use links unless their integration explicitly supports automatic closure at the configured event. Resolve missing policy before adding automatic closure or performing an otherwise undecided delivery action; continue drafting and review meanwhile. Merge and ticket closure need their own authorization beyond a PR-body task; when they are in scope, follow the same policy and verify the resulting state.

Workflow

1. Resolve the target change request from the user-provided URL or current branch. When creating one, use the intended head and base branches.
2. Inspect commits, diff size, changed paths, generated files, and the existing title and description.
3. Identify reviewability issues: noisy commits, stale description, unrelated changes, mixed mechanical and logic changes, missing tests, or unclear reviewer entry points. When the change is too large for notes to make it reviewable, recommend splitting it.
4. For a review-only request, stay read-only on the branch and the code host: assess the change request against the title, body, and history guidance below and return concrete findings and missing evidence. When correctness and maintainability review is also requested, load and apply code-review and report these findings with its result; without that skill, review those concerns directly at the same standard and note that it is missing.
5. When creating or updating a change request, address the issues within the requested scope through the description and review notes; a body-only request leaves the title and history as they are. Restructure commits only through History Cleanup below. Done when the description matches the current diff and the tree still matches the intended code.
6. For title creation or updates, derive and validate the title using the rules below. Publish it through the configured code host's explicit title argument or field. Read back the published title and correct any mismatch.

Change request titles

Repository title rules, from the title policy in docs/agents/code-host.md, root instructions, or contribution guidance, take precedence over these defaults.