submit-epic

Run final validation and submit a pull request for completed epics.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lenlla/one_shot_build --skill submit-epic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: submit-epic
Source: https://github.com/lenlla/one_shot_build/tree/main/skills/submit-epic
Command: npx skills add https://github.com/lenlla/one_shot_build --skill submit-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures completed epics meet the project's Definition of Done and quality standards before creating a pull request and reporting results to the orchestrator, removing manual finalization steps.

Core Features & Use Cases

  • Definition of Done Enforcement: Runs a DoD checklist and classifies failures into superficial vs code-level issues with retry behavior for superficial fixes.
  • Quality Scanning and Auto-fixes: Executes a quality scan, applies trivial fixes in autonomous mode, and includes remaining findings in PR metadata.
  • PR Creation and Optional Auto-merge: Commits final state, creates a PR for the epic branch, and can auto-merge in autonomous mode while reporting status back to the orchestrator.

Quick Start

Use the submit-epic skill to run DoD checks and a quality scan, commit final changes, open a PR for epic/<epic-name>, and report DoD results, scan findings, and merge status to the orchestrator.

Frequently Asked Questions about submit-epic

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

FAQPage Schema
How do I automate Definition of Done checks before opening a pull request?

To automate Definition of Done checks before opening a pull request, you can run a final validation skill that executes a DoD checklist, classifies failures into superficial or code-level issues, and applies automated retries for superficial fixes before committing.

Can I auto-merge a pull request after a quality scan passes?

Yes, you can auto-merge a pull request after a quality scan passes by using an autonomous mode that commits the final state, creates a PR for the epic branch, and optionally auto-merges while reporting the status back to the orchestrator.

What is the best way to handle superficial quality scan failures during epic submission?

The best way to handle superficial quality scan failures during epic submission is to apply automated trivial fixes in autonomous mode, retrying the validation steps to ensure the epic meets quality standards before creating the pull request.

Does the epic submission process include quality scan findings in the PR metadata?

Yes, the epic submission process includes remaining quality scan findings in the pull request metadata, ensuring that any non-trivial issues detected by the quality scan are reported alongside the DoD results to the orchestrator.

How do I report DoD results and merge status back to an execute-plan orchestrator?

You can report DoD results and merge status back to an execute-plan orchestrator by running an epic-level workflow that performs final validation, submits the pull request, and generates a structured report of the DoD checks, scan findings, and merge outcome.