Harness Kit

skill

yeet

End-to-end "ship it to the remote": read worktree, classify changes, tidy debris, split semantic commits, and push. Judgment layer over git, not a wrapper; decides what belongs and how reviewers should read the diff. Use when: "yeet", "yeet this", "commit and push", "ship local changes", "tidy and commit", "wrap this up and push", "get this off my machine". Trigger: /yeet, /ship-local (alias).

/yeet

Source: skills/yeet/SKILL.md

What it does

End-to-end "ship it to the remote": read worktree, classify changes, tidy debris, split semantic commits, and push. Judgment layer over git, not a wrapper; decides what belongs and how reviewers should read the diff. Use when: "yeet", "yeet this", "commit and push", "ship local changes", "tidy and commit", "wrap this up and push", "get this off my machine". Trigger: /yeet, /ship-local (alias).

Workflow role

Ship primitive in the Harness Kit operating loop.

Source contract preview

This generated excerpt gives readers the beginning of the live primitive contract before they jump to GitHub.

Take the current worktree state → one or more conventional commits → remote.
One command. Executive authority. No approval gates.

## Stance

1. **Act, do not propose.** The skill has authority within its domain. Stage
   what belongs, leave out what doesn't, delete debris, split logically, push.
   Escalate only on red-flag state (see Refuse Conditions).
2. **Clean tree is the deliverable.** `/yeet` is not done while visible paths
   remain. Shared Closeout applies; resolve every path by commit, ignore, move
   out of the repo, or delete. See `harnesses/shared/AGENTS.md` (Closeout).
3. **Reviewability is the product.** A stack of three focused commits beats
   one 2,000-line "wip" commit, every time. Split on semantic boundaries
   even if the tree was built in one session.
   Provider-roster receipts are part of classification evidence when present.
   If classification requires substantive judgment and no receipts exist,
   dispatch two or more roster members before packaging completed work.
4. **Never lose work.** Untracked scratch that might be the user's in-flight
   thinking gets moved, not deleted, unless it's unambiguous debris.
5. **Conventional Commits, always.** Type, optional scope, imperative subject.
   Body explains *why*, not *what*.

## Delegation Floor

Delegation floor applies: probe the roster first; dispatch two or more
providers for substantive work; direct solo only for mechanical, emergency,
user-forbidden, or fewer-than-two-providers cases. See
`harnesses/shared/AGENTS.md` (Roster).

Local lane guidance: Use lanes for diff classification and risk review; withhold final commit intent until synthesis, then the lead owns staging, messages, verification, and receipts.

## Modes

- Default: stage → split into commits → push.
- `--dry-run`: report the plan (commit boundaries, messages, skips), do not execute.
...

What to verify