Menu
Turn local Gradient worktree changes into coherent commits and push when appropriate. Trigger: /yeet, /ship-local.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Maintain Gradient's repo-local agent harness: skills, agents, settings, repo brief, and gate-aligned instructions. Trigger: /harness, /skill, /primitive.
Take one shaped Gradient docs/schema/profile task to merge-ready. Composes /shape, /implement, /code-review, /ci, /qa, /demo, and /refactor as needed. Stops before merge. Trigger: /deliver.
Assess Gradient's readiness for governed agent work across docs, schemas, profiles, harness, validation, evidence, and public-safe boundaries. Trigger: /agent-readiness, /readiness.
Dialectical premise-and-alternatives audit for a plan, spec, or context packet. Four moves: premise challenge (is this the right problem?), mandatory structurally-distinct alternatives, cross-model outside voice, user-ratified convergence. Named for Gary Tan's plan-ceo-review pattern; operationalizes the AGENTS.md "Diverge Before You Converge" doctrine at the plan-review stage. Use when: about to commit to a plan/spec/design, reviewing a ticket before shape, when "is this the right problem" would be useful, or any time a proposal smells like a symptom fix instead of a root-cause fix. Trigger: /ceo-review, /challenge, /premise-check.
Gradient gate audit and validation workflow. Use when checking whether a docs/profile/schema change is safe to ship in this scaffold. Trigger: /ci.
Review Gradient docs, profiles, schemas, and harness changes for public-safe boundaries, lifecycle consistency, and contract depth. Trigger: /code-review, /review, /critique.
| 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 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.
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.
docs: clarify Gradient policy feedback loopschema: add evidence packet contractharness: tailor repo skillsCustomer data, private repo names, credentials, access tokens, real telemetry, meeting transcripts, or deployment-specific configs.