Harness and Skills Reference

The reuse-worktree modifier tells the skill the daemon already ran git worktree add and installed dependencies. The agent calls worktree-setup.sh --reuse, which exports the worktree path variables without touching git.

Six steps: (1) fetch issue from internal HTTP store, (2) resolve shipping mode, (3) worktree setup via --reuse, (4) implement and run quality gate, (5) update docs, (6) commit + push + gh pr create. The PR body never contains "Closes #N" -- Slop closes the issue directly via closeWorkerIssue().

# Step 1 - fetch issue (never gh issue view -- numbers collide)
GET $SLOP_URL/api/internal-issues?repo=$SLUG
# filter: .find(i => i.number === N)

# Step 6 - commit and ship (remote mode)
git commit -m "feat: <summary>"
git push -u origin slop/issue-<N>
gh pr create --title "..." --body "..."

Rebases onto the latest base, reproduces the failing check, fixes the root cause, and force-pushes. The existing PR updates automatically. Never opens a new PR. Never uses git stash or git rebase -i (interactive mode is not supported in unattended sessions).

git fetch origin <base> && git rebase origin/<base>
# reproduce, fix, then:
git push --force-with-lease

Rebases onto the base branch and resolves every conflict in place, preserving the intent of both sides. Runs lint, typecheck, and tests as a fast sanity check, then force-pushes (remote) or leaves the branch clean (local mode, no push).

Reads .slop-verify-context.json written by the daemon before launching the session:

{ "issueNumber": 42, "implementGateSha": "abc123", "docsOnly": false }

If implementGateSha matches HEAD, tests were already green at the end of the implement session -- the verify-gate skips re-running tests and goes straight to /review. Always ends with exactly one line: SLOP_VERDICT: pass or SLOP_VERDICT: findings.

The PR is assumed wrong until proven otherwise. Three rules: (1) every finding cites file:line from the diff or source, (2) collect findings first, add fixes after verification, (3) style never blocks a merge.

Posts one COMMENT-event review with inline comments all prefixed reviewer:. Verdict line:

reviewer: **Verdict: pass**
-- or --
reviewer: **Verdict: request_changes**

On re-review (after /address-comments): walks all threads and resolves settled ones via GraphQL resolveReviewThread.

Reads every reviewer: thread and responds to each finding individually. For each finding it either fixes (edits code, stages, replies addresser: fixed in <sha>), declines (addresser: declined - <file:line evidence>), or questions (addresser: question - ...). All fixes are pushed in one git push at the end, then a wrap-up summary comment is posted at the PR top level. Worker returns to waiting_ci after addressing.