yeet

name	yeet
description	Turn local Gradient worktree changes into coherent commits and push when appropriate. Trigger: /yeet, /ship-local.
argument-hint	[--dry-run] [--single-commit] [--no-push]

/yeet

/yeet is a commit judgment layer, not a git wrapper. In this repo, commits should separate docs, schema/profile, fixture, and harness changes when that makes review clearer.

Gate

The load-bearing ship gate is ./scripts/validate.sh, plus reviewer judgment for lifecycle semantics in docs/architecture.md and docs/module-contracts.md when docs change.

Procedure

1. Read the whole worktree diff.
2. Exclude private or ignored deployment files.
3. Group changes by lifecycle stage and artifact type.
4. Run the current gate checks before committing when feasible.
5. Use conventional messages such as:
   • docs: clarify Gradient policy feedback loop
   • schema: add evidence packet contract
   • harness: tailor repo skills
6. Preserve work references manually until a tracker exists.

Never Commit

Customer data, private repo names, credentials, access tokens, real telemetry, meeting transcripts, or deployment-specific configs.