Install any skill in seconds. Free to start, no credit card required.
Get Started Free →catlog22/maestro-merge
Merge session worktree branch back to main
Passed 13 of 19 test cases with the skill, and 5 of 19 without it.
and 11 more in the full report
11 fixed5 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
If a user executes session merge with `--continue` when no active unresolved git merge state exists, what error code is returned?
| Checked | Without skill | With skill |
|---|---|---|
| Emit error code E003. | Missed | Passed |
The instructions your model reads when the skill loads.
<required_reading>
@/.maestro/workflows/run-mode.md
@/.maestro/workflows/codex-run-mode.md
</required_reading>
Terminology: this command uses 'session' throughout. The underlying workflow file (merge.md) may use 'milestone' as a legacy alias for 'session'. Treat them as equivalent: --session maps to workflow's -m, state.json.sessions[] maps to state.json.milestones[].
Flags (--session, --force, --dry-run, --no-cleanup, --continue), merge sequence, artifact sync detail, and conflict handling are defined in workflow merge.md.
--dry-run short-circuit: execute GATE 1 health check only, display merge preview (files that would change, artifact sync plan), then EXIT before rebase/merge. GATE 2 and GATE 3 are not reached.
GATE 1: Pre-merge → Git Merge
Note on --force: skips user confirmation for incomplete phase artifacts (W002). Does NOT skip conflict resolution or rebase. Specifically: GATE 1 and GATE 2 are unaffected by --force; GATE 3's artifact completeness check uses --force to bypass the W002 confirmation.
GATE 2: Git Merge → Artifact Sync
GATE 3: Artifact Sync → Completion
sessions/{session_id}/runs/.test cases passed, vs 5 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.