Produce a compact, zero-context handoff for the current Codex or Pi work and save it to the requested destination, active task conclusion, or a new task summary file. Use when the user asks to preserve progress for a later session.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this as the Codex and Pi equivalent of /up:summary. Work from the current conversation, task file, git state, and repository; do not assume a Claude JSONL transcript exists.
docs/tasks/*.md, if one exists.## Conclusion in the active task file. If there is no active task, create docs/tasks/summary-<slug>.md. Ask only when the destination is ambiguous.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Run a bounded implement-attack-repair loop for a user-specified task. Use when work needs repeated independent criticism: perform the task, dispatch a fresh attacker, verify significant findings, repair them, and stop on a clean attack or the user's round limit.
The English summary is being prepared. Showing the original description.
Explain a file, error, design, diff, or concept like a helpful engineering colleague: grounded in evidence, concise, and with useful follow-up threads. Use when the user asks for a clear explanation of the current work or codebase.
The English summary is being prepared. Showing the original description.
Turn one user criticism into a principle-level fix: find the violated principle, every similar occurrence, and fix the shared cause. Use only when the user explicitly invokes expand, $expand, /up:expand, or /skill:expand.
The English summary is being prepared. Showing the original description.
Use when a task needs an isolated checkout. Verify the worktree location, keep mutable environments and build outputs local, and run only authorized setup and checks.
The English summary is being prepared. Showing the original description.
Contract for hands-off mode — the ultrapack workflow variant that minimizes user prompts after Design, takes the safest reversible path, and logs every auto-choice for one end-of-task review. Referenced by the workflow entry point and child skills (udesign, uplan, uexecute, uverify, ureview). Read when the task file's **Mode:** header is `hands-off`.
The English summary is being prepared. Showing the original description.
Use when the user explicitly asks to launch and supervise a job. Require an authorized launch, monitoring, recovery, and teardown contract. Detect failures without inventing permission to restart or spend money.
The English summary is being prepared. Showing the original description.