oneshot

Execute defined tasks end-to-end with incremental commits and final summaries.

11|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/zig-whatwg/crane --skill oneshot-zig-whatwg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oneshot
Source: https://github.com/zig-whatwg/crane/tree/main/skills/oneshot
Command: npx skills add https://github.com/zig-whatwg/crane --skill oneshot-zig-whatwg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Oneshot enables complete, uninterrupted execution of well-defined tasks from start to finish, eliminating the need for confirmations or status updates mid-progress.

Core Features & Use Cases

  • Silent, end-to-end execution: Work through all subtasks without interrupts.
  • Incremental commits: Changes are committed in small, reversible units following a strict commit workflow.
  • Final summary & issue handling: A comprehensive summary is produced and issues are updated or created for incomplete work at the end.

Quick Start

Use the oneshot skill to complete a defined epic (e.g., "oneshot bd-42"). The skill will run to completion and return a final summary.

Frequently Asked Questions about oneshot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-to-end task execution for feature implementation without intermediate prompts?

End-to-end task execution without intermediate prompts is handled by the oneshot skill, which processes clearly scoped epics from start to finish. It completes all linked subtasks silently and produces a final summary without mid-progress confirmations.

What is the best way to execute bugfix workflows across multiple linked issues in one run?

Executing bugfix workflows across linked issues in one run requires a clearly defined scope in the SKILL.md frontmatter. The skill processes all subtasks continuously, committing changes in small reversible units, and updates issues for any incomplete work at the end.

Do I need the Zig toolchain and commit workflow to run automated end-to-end task execution?

Yes, automated end-to-end task execution requires the Zig toolchain, commit_workflow, pre_commit_checks, and beads_workflow. These dependencies ensure changes follow a strict commit workflow and that task scope is properly determined from the SKILL.md frontmatter.

How does silent end-to-end execution handle incremental commits and issue tracking?

Silent end-to-end execution handles incremental commits by saving changes in small, reversible units following a strict commit workflow. Upon completion, it produces a comprehensive summary and automatically updates or creates issues for any incomplete work.

When should I avoid using uninterrupted execution for automated task workflows?

You should avoid uninterrupted execution for automated task workflows when tasks lack clear scoping in the SKILL.md frontmatter or when the required Zig toolchain, commit_workflow, pre_commit_checks, and beads_workflow dependencies are not properly configured.