Open a PR

Prepare a narrow, landable pull request, open it ready for review, and babysit it to merge readiness. Return its URL and final status.

Worktree

Read the repository instructions and determine the intended base, branch policy, PR tooling, and commit and PR conventions. Where the repository sets a commit convention or PR template, follow it instead of the ones below. Use the current worktree when its changes are the PR, creating the intended branch there if needed. Otherwise prefer an isolated worktree from the base branch. Never patch out, reset, discard, or overwrite user work without approval; stop and ask when the worktree mixes the PR's changes with unrelated work or is snarled.

Inspect the status, staged and unstaged diffs, every untracked file, branch ancestry, commit range, and remote state. Verify that every change belongs to the requested PR. Stop on ambiguous scope, merge conflicts, sensitive data, missing permission, or an unsafe history rewrite.

Commits

Plan small, ordered commits that tell the story. Each commit should be independently reviewable and landable. Amend when a fix belongs in a just-made, unshared commit; create a new commit when it is separable. Ask before rebasing shared work or force-pushing.

Run deslop on the exact intended diff before each commit. Run no-comments on the complete PR diff before review. Replan and rerun deslop on changes produced by accepted comment findings.

Write commit subjects using Conventional Commits. Name the changed area as the scope. Keep the subject short and imperative, name a real symbol when useful, and omit the trailing period. A commit body explains facts not present in its subject; it never restates the subject. Apply unslop to every subject and body without changing the Conventional Commit syntax.

Use ship for each commit and push, naming the changes that belong in that commit.