auto-push

Coordinate Plan, Build, and Wrap-up phases after a single plan approval.

1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Joaovsales/coding-agent-workflow --skill auto-push-joaovsales
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-push
Source: https://github.com/Joaovsales/coding-agent-workflow/tree/main/.agents/skills/auto-push
Command: npx skills add https://github.com/Joaovsales/coding-agent-workflow --skill auto-push-joaovsales

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables a controlled, semi-autonomous pipeline that requires a single plan approval before autonomous execution of build and wrap-up, eliminating back-and-forth prompts.

Core Features & Use Cases

  • Enforces a single pre-flight plan approval gate before auto-execution of the pipeline.
  • Coordinates Plan → Build → Wrap-up with safety gates, test verifications, and artifact creation.
  • Use Case: teams describe a feature, approve once, and have the pipeline complete with minimal manual intervention.

Quick Start

Describe a feature, approve the plan with 'y', and watch the autonomous build and wrap-up complete.

Frequently Asked Questions about auto-push

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

FAQPage Schema
How do I set up an automated build pipeline that only needs one approval before hands-free deployment?

An automated build pipeline with a single approval gate requires a plan, build, and wrap-up phase structure. You approve the initial plan once, and safety gates handle test verification and artifact creation autonomously.

What is a pre-commit gating mechanism for autonomous execution steps?

A pre-commit gating mechanism enforces a strict plan approval before allowing autonomous execution steps to proceed. It eliminates manual back-and-forth prompts by requiring a single confirmation to trigger the build and wrap-up.

Can I use a semi-autonomous pipeline for feature development workflows with safe overrides?

Yes, a semi-autonomous pipeline suits feature development workflows by applying Phase C policies for safe overrides. It coordinates e2e checks and safety gates after the initial plan approval to ensure secure execution.

How do I stop manual prompts from interrupting my deployment pipeline after the initial plan approval?

To stop manual prompts from interrupting your deployment pipeline, implement an approve-once policy. A single plan approval triggers hands-free execution of build and wrap-up phases without further intervention.

What are the limitations of using a single approval gate for autonomous build and deployment?

The limitation of a single approval gate is that all safety checks must be configured within the build and wrap-up phases beforehand. Once approved, execution is hands-free, so missing pre-configured safety gates cannot be manually intercepted.