How do I install the Integrate Worker skill?

Run npx skillmds@latest add tomevault-io/integrate-worker in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Integrate Worker safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Integrate Worker?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Integrate Worker free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Integrate Worker?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Integrate Worker by tomevault-io — Agent Skill

Name: Integrate Worker
Author: tomevault-io

Integrate Worker

Integrate a worker agent's diff onto fresh trunk — apply, verify repros by hand, cross-check interacting mechanisms, full suite, ship + queue. Use after any worktree worker (fix cycle, hunt follow-up) returns a diff file. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Integrating a worker diff

Battle-tested protocol from the 2026-06 autonomous runs (~30 PRs integrated). Each step exists because skipping it once caused a real failure.

Steps

Fresh trunk, always. jj git fetch && jj new 'trunk()' then git reset --quiet — the colocated git index goes stale after jj working-copy switches and makes git apply --3way fail with "does not match index".
Apply with 3-way fallback. git apply --3way /tmp/<worker>.diff. Conflicts mean the worker's base predates trunk changes — resolve by intent, not by side: a worker editing code that trunk deleted usually means the worker's edit is subsumed (keep the deletion); append-append conflicts in test TOML files keep both case sets.
Re-verify the repros yourself. Build (bash scripts/rue build) and run every repro the worker claims to fix, on this checkout, by execution. A worker's "full suite green" was true in its worktree against its base — not here. Workers have shipped fixes verified against stale drafts of trunk; only integration-time re-verification catches that.
Write the cross-mechanism test. If this worker and another (landed or in-flight) built interacting mechanisms — e.g. one added per-field drop flags while another added drop-on-overwrite — write a test that exercises the combination NOW. The workers' own suites cannot see the seam; twice in one night, individually-green workers were jointly wrong (double-drops).
Full suite + format. ./test.sh must exit 0; bash scripts/rue fmt.
Ship + queue. jj describe (subject + why + what was verified), jj git push -c @, gh pr create --repo rue-language/rue --base trunk --head steveklabnik:<bookmark> with one Fixes RUE-NN per line (a comma list only closes the first), gh pr merge <n> --auto. Use Part of RUE-NN when items remain — and remember "Part of" strands the issue In Progress (sweep afterwards per CLAUDE.md).
Queue bounces (DIRTY after a sibling merges): jj rebase -s <change> -d 'trunk()', resolve keeping BOTH PRs' semantics, re-run step 3's repros plus the sibling's, full suite, push the bookmark, re-arm --auto. Never force-push a branch that is actively queued without re-arming.

Worker-prompt invariants this protocol assumes

Workers were told: reproduce first, refutations are as valuable as fixes, file ownership is by region, output is git diff <base> HEAD to an OUTFILE plus a .meta summary. If integrating a diff produced under weaker rules, treat every claim as unverified.

Source: rue-language/rue — distributed by TomeVault.

---name: integrate-workerdescription: Integrate a worker agent's diff onto fresh trunk — apply, verify repros by hand, cross-check interacting mechanisms, full suite, ship + queue. Use after any worktree worker (fix cycle, hunt follow-up) returns a diff file. Use when this capability is needed.---# Integrating a worker diffBattle-tested protocol from the 2026-06 autonomous runs (~30 PRs integrated).Each step exists because skipping it once caused a real failure.## Steps1. **Fresh trunk, always.** `jj git fetch && jj new 'trunk()'` then `git reset --quiet` — the colocated git index goes stale after jj working-copy switches and makes `git apply --3way` fail with "does not match index".2. **Apply with 3-way fallback.** `git apply --3way /tmp/<worker>.diff`. Conflicts mean the worker's base predates trunk changes — resolve by *intent*, not by side: a worker editing code that trunk deleted usually means the worker's edit is subsumed (keep the deletion); append-append conflicts in test TOML files keep both case sets.3. **Re-verify the repros yourself.** Build (`bash scripts/rue build`) and run every repro the worker claims to fix, on this checkout, by execution. A worker's "full suite green" was true *in its worktree against its base* — not here. Workers have shipped fixes verified against stale drafts of trunk; only integration-time re-verification catches that.4. **Write the cross-mechanism test.** If this worker and another (landed or in-flight) built *interacting* mechanisms — e.g. one added per-field drop flags while another added drop-on-overwrite — write a test that exercises the combination NOW. The workers' own suites cannot see the seam; twice in one night, individually-green workers were jointly wrong (double-drops).5. **Full suite + format.** `./test.sh` must exit 0; `bash scripts/rue fmt`.6. **Ship + queue.** `jj describe` (subject + why + what was verified), `jj git push -c @`, `gh pr create --repo rue-language/rue --base trunk --head steveklabnik:<bookmark>` with one `Fixes RUE-NN` **per line** (a comma list only closes the first), `gh pr merge <n> --auto`. Use `Part of RUE-NN` when items remain — and remember "Part of" strands the issue In Progress (sweep afterwards per CLAUDE.md).7. **Queue bounces** (DIRTY after a sibling merges): `jj rebase -s <change> -d 'trunk()'`, resolve keeping BOTH PRs' semantics, re-run step 3's repros plus the sibling's, full suite, push the bookmark, re-arm `--auto`. Never force-push a branch that is actively queued without re-arming.## Worker-prompt invariants this protocol assumesWorkers were told: reproduce first, refutations are as valuable as fixes,file ownership is by region, output is `git diff <base> HEAD` to an OUTFILEplus a `.meta` summary. If integrating a diff produced under weaker rules,treat every claim as unverified.---> Source: [rue-language/rue](https://github.com/rue-language/rue) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions