turbo-completion

Automate end-to-end software delivery from verification through merge and cleanup.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/devseunggwan/praxis --skill turbo-completion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: turbo-completion
Source: https://github.com/devseunggwan/praxis/tree/main/skills/turbo-completion
Command: npx skills add https://github.com/devseunggwan/praxis --skill turbo-completion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end software delivery by coordinating verification, code review, PR creation, merge, and cleanup in a single automated pass.

Core Features & Use Cases

  • Auto-detects PR state to pick the right pipeline (verify-only, full pipeline, or merge-only).
  • Orchestrates verification, code review routing, PR creation, inline context compounding, and post-merge cleanup.
  • Supports standalone verify mode or a complete lifecycle with optional learning capture for improvements.

Quick Start

Initiate turbo-completion from your current git state to run the appropriate delivery pipeline.

Frequently Asked Questions about turbo-completion

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

FAQPage Schema
How do I automate the entire pull request lifecycle from verification to merge?

You can automate the pull request lifecycle by orchestrating verification, code review, PR creation, merge, and cleanup in a single automated pass. The workflow auto-detects PR state to execute the appropriate pipeline.

What is single-pass software delivery and when do I need it?

Single-pass software delivery coordinates verification, code review, PR creation, merge, and cleanup together. You need it when your software team requires a fully automated workflow that adapts to verify-only, full pipeline, or merge-only scenarios.

Can I run code review and PR creation automatically from my current git state?

Yes, you can run code review and PR creation automatically from your current git state. The process requires git state awareness and PR tooling integration to initiate the appropriate delivery pipeline.

How does a workflow handle different PR states like verify-only versus full merge?

The workflow auto-detects the current PR state to pick the right pipeline, adapting dynamically to verify-only, full pipeline, or merge-only scenarios. This ensures the correct execution mode applies based on the detected branch condition.

Do I need specific PR tooling integration to automate post-merge cleanup?

Yes, PR tooling integration is required to automate post-merge cleanup effectively. The automated delivery workflow depends on this integration to coordinate the final cleanup phase after a successful merge.

What is the best way to manage a complete delivery cycle without manual intervention?

The best way to manage a complete delivery cycle without manual intervention is using a pluggable execution mode with built-in verification. This orchestrates the full pipeline while capturing optional learning for future improvements.