one-shot

Orchestrates a nine-step pipeline from ticket to merged PR for small changes.

5|1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/ai-hero/hero-skills --skill one-shot-ai-hero
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: one-shot
Source: https://github.com/ai-hero/hero-skills/tree/main/skills/one-shot
Command: npx skills add https://github.com/ai-hero/hero-skills --skill one-shot-ai-hero

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Small development tasks still require a long manual loop: planning, branching, implementing, testing, pushing, self-reviewing, responding to review comments, and merging. This Skill chains the existing hero-skills commands into one automated pipeline so a small ticket or description becomes a merged PR without manual step-by-step coordination. ## Core Features & Use Cases - End-to-end pipeline orchestration: Runs plan, implement, simplify, push (with tests), self-review, mark-ready, await-review, respond, and ship as a single DAG with progress rendering. - Resume detection: Inspects git, PR, and work-item state to infer the correct resume step, so interrupted sessions continue without re-running completed steps. - Scope guard and safety gates: Refuses multi-item or one-way-door work, halts on failed child steps, and requires user confirmation at mark-ready and merge gates. - Use Case: A developer runs the skill with a Linear ticket ID like PROJ-123; the skill plans the work-item, implements it on an auto-created branch, runs tests, opens a draft PR, self-reviews, responds to bot comments, and merges after approval. ## Quick Start Run the one-shot skill with a ticket ID or short task description, such as asking it to take PROJ-123 from ticket to merged PR.

Frequently Asked Questions about one-shot

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

FAQPage Schema
How do I take a ticket to a merged PR automatically?

Run the one-shot skill with an issue ID like PROJ-123 or a plain-text description. It plans the work-item, implements it on an auto-created branch, runs tests, pushes a draft PR, self-reviews, responds to review comments, and merges after approval.

What happens if a one-shot run is interrupted mid-pipeline?

The skill detects resume state from git, PR status, and work-item files on the next invocation. It infers the correct step from a decision table and continues from there without re-running completed steps.

What are the prerequisites for running this pipeline?

You need GitHub CLI authenticated with the repo scope, a HERO.md config from init-hero, the pr-review-toolkit plugin for self-review agents, and Playwright MCP for UI smoke tests. The auto-approve workflow must also exist on the default branch.

When should I not use one-shot for a task?

Avoid it for large or risky work: the scope guard stops the run if planning produces more than one work-item or the item is flagged one_way_door. Larger efforts should go through the wayfare pipeline instead.

Why does one-shot stop at the mark-ready or merge step?

Those are deliberate user gates, not errors. The pipeline pauses for your confirmation before marking a PR ready and before merging, and declining either gate halts the run with the failed node marked in the DAG.