Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ganyuanran/finishing-a-development-branch
Use when verified work has an Aegis-created branch/worktree to integrate or clean up, or the user explicitly requests merge, PR, or branch lifecycle handling.
Passed 13 of 20 test cases with the skill, and 9 of 20 without it.
and 9 more in the full report
7 fixed7 passed either way5 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/19/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to start working on a brand new isolated feature called user-profile. Please set up a new Git worktree at ../worktrees/user-profile off the main branch and switch me to it so I can begin coding.
| Checked | Without skill | With skill |
|---|---|---|
| Create the requested Git worktree at the specified directory path. | Missed | Passed |
| Avoid running branch teardown, disposition, or worktree deletion steps. | Passed | Passed |
The instructions your model reads when the skill loads.
Integration choice and checkout lifetime are separate. Verify first, mutate only task-owned resources, then prove what was removed or retained.
Core principle: fresh evidence -> authorized integration -> ownership-aware cleanup -> Git/path readback.
Announce at start: explain which branch/worktree lifecycle is being closed.
Read the task's TaskStartSnapshot and current repository state. Record:
HEAD, branch/detached state, upstream divergence, and active Git ops;git worktree list --porcelain;Stop on conflicts, unexplained detached state, failed verification, dirty/untracked state in
a cleanup target, or unknown ownership. Do not infer the base from the names
main or master; use task records, repository authority, or explicit user
direction. Never auto-stash, reset, clean, pull, rebase, amend, force-push, or
bypass hooks.
For a trusted host-managed detached checkout, follow the repository's approved managed-workspace contract: verify host binding, default cwd, root, and HEAD; then use its scoped local-commit and native handoff path. Report detached HEAD in the receipt. This exception does not authorize automatic deletion of the detached checkout or bypass unknown ownership/binding.
If no task-created branch/worktree exists and integration was not requested,
skip this workflow: report the local task commit plus Task clean and
Repository clean; do not invent merge/PR ceremony.
Run the smallest current-authority test set that proves the completed task. If
test cases passed, vs 9 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.