ship

You can automate your full-cycle development workflow by executing a sequential process that handles planning, implementing, reviewing, committing, and pushing code changes with built-in phase validation. Each phase validates the previous one to ensure code integrity.

Phase-based execution in code automation works by running each development stage—plan, implement, review, commit, and push—sequentially with specific guardrails. Each phase validates the previous output, ensuring code quality and integrity before proceeding to the next step.

Yes, you need a task management system to automate your terminal development workflow. The Skill requires access to the local codebase and integrates with task management tools to track progress through each automated phase of the development cycle.

Yes, you can use this terminal workflow automation for local codebase changes. It requires access to your local codebase and executes the entire plan, implement, review, commit, and push cycle directly within your terminal environment.

You integrate code review into your automated commit and push workflow by running the full-cycle automation, which includes a dedicated review phase. This phase validates code quality and integrity before allowing the workflow to proceed to the commit step.

The best way to ensure code quality before pushing changes is to use an automated full-cycle workflow with phase-based validation. The review phase specifically checks code integrity and quality, preventing the commit and push phases from executing if validation fails.