Full Send
The user invoked this because they are not watching this thread and want the
work done end-to-end. Your updates and your final message go unread until long
after you stop. You own the work from its current state to a merged PR.
The user grants you permission to:
- Merge the PR once the merge gate passes.
- Force-push the PR's own branch with after a rebase.
- Use the test methods that Proof needs, without asking first.
Testing permission
Invoking this skill is the permission. If a project file or other instruction
says to ask before a test method, or to leave testing to the user, this request
replaces that rule for this task.
That includes ask-first rules for computer use, browser automation, simulators
and devices, running the app or a dev server, screenshots, and visual checks.
Use the method that gives direct proof. List it in the report.
Rules about how to test still apply. Follow rules that name the correct
command, fixture, or check. This permission only removes the ask-first or
leave-it-to-the-user step. If a preferred method cannot prove the change, use a
gated method under this permission.
It covers only the tests needed for this task. It does not add permission for
the steps under "Asking the user", such as production changes or data deletion.
It also does not bypass a harness or system approval prompt if one appears.
Steps
- Finish the change. Complete the goal from the user's request with the
smallest change that works. Fix the case that happened, not every case that
could. If you are on the default branch, create a branch first.
- Prove it. Get proof for every change you made. See "Proof".
- Get feedback. Use the skill to verify changes. Re-prove any
behavior a fix touches.
- File the PR with the skill. Rebase onto the latest default
branch first. Add one short line to the description that says how you proved
the change.
- Babysit the PR with the skill. Fix CI failures and real
human review findings. Get proof for each fix before you push it.
- Merge when the merge gate passes.
- Report in your final message: the PR link, the merge commit, your proof,
and each decision you made for the user.
Stay active from step 1 to step 7. If you end your turn while checks are
pending, the work stops, because nobody will prompt you again. Wait with the
watcher from
, so something wakes you when the PR changes. In T3
Code that is
. If you stop before the merge, call
first.
Proof
Proof is evidence you observed yourself in this session: command output, a
reproduction, a screenshot. Use the most direct proof the change allows:
- Reproduce the original failure, apply the fix, then watch the same
reproduction pass.
- Run the checks that the repo's CI runs (typecheck, lint, tests).
- Add one focused test that fails without the fix, when the behavior has none
and the repo has a test setup.
- For UI and runtime behavior, run the app and look at the change. Green mocked
tests do not prove that the user experience works. Attach screenshots to the
PR when they help and you have a way to upload them.
When you cannot find a way to prove a change, you do not have full confidence.
Ask the user.
Merge gate
Full confidence means all of these are true on the latest commit:
- Your proof covers every change in the diff.
- Required checks are green.
- Every review comment is fixed or answered with a written reason, and no
review thread is unresolved.
- No human review still requests changes.
- The branch is up to date with the default branch, and GitHub reports it as
mergeable.
Merge with the method the repo uses. Check the allowed methods and recent merged
PRs. If the repo uses a merge queue or auto-merge, stay until GitHub reports the
PR as merged. Merge through branch protection as configured. Never use
or other bypasses.
Asking the user
A question in a normal message goes unseen, and the thread looks done. To ask
the user something, use the harness's question tool so the thread shows that it
is waiting:
in Claude Code,
in Codex, or
the question tool your harness has. Put all the context in the question: the PR
link, what blocks you, and the options with your recommendation first.
Ask only when you cannot continue alone:
- You cannot prove the change.
- The merge gate cannot pass, and you cannot fix that yourself.
- The next step is outside the grant above: deleting data, touching production,
changing things outside the repo, closing a PR, or force-pushing any other
branch.
- The goal is ambiguous in a way that changes the result.
- Another PR makes this one obsolete.
Decide everything else yourself with sensible defaults, and list those decisions
in the report.
If no question tool is available, or the tool returns no answer, take the safe
path: leave the PR open and unmerged, and start your final message with the
question.