execute

Execute code tasks through worker implementation, parallel reviews, and commit generation.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/metalspawn/claude-ops --skill execute-metalspawn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: execute
Source: https://github.com/metalspawn/claude-ops/tree/main/skills/execute
Command: npx skills add https://github.com/metalspawn/claude-ops --skill execute-metalspawn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the execution of code tasks, ensuring code quality through a rigorous, multi-agent review and validation pipeline before committing.

Core Features & Use Cases

  • Task Execution: Runs code implemented by a worker agent based on task descriptions.
  • Parallel Review Gates: Employs code-reviewer, semantic-reviewer, and validator agents simultaneously to check code against conventions, clarity, and functionality.
  • Automated Committing: Applies detected commit conventions and commits code only after all review gates pass.
  • Use Case: After a plan is created, use /orc:execute to have the worker implement the code for a task, followed by automated checks for code style, semantic correctness, and passing tests before a commit is made.

Quick Start

Use the execute skill to run the current task through the worker and review pipeline.

Frequently Asked Questions about execute

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

FAQPage Schema
How do I automate code execution and reviews before committing?▼

Automating code execution and reviews involves running worker-implemented tasks through parallel code, semantic, and validation checks, generating a commit only after all review gates pass.

What is an automated commit pipeline with parallel review gates?▼

An automated commit pipeline with parallel review gates uses simultaneous code-reviewer, semantic-reviewer, and validator agents to check conventions, clarity, and functionality before allowing a commit.

How do I enforce commit conventions during task automation?▼

Enforcing commit conventions during task automation requires the pipeline to detect existing commit conventions and strictly apply them, blocking commit generation until all validation rules are satisfied.

Can I run verification tasks separately from the code review pipeline?▼

Verification tasks can run separately by relying solely on the validator agent, bypassing the code-reviewer and semantic-reviewer agents used in the standard execution pipeline.

Why does my automated commit fail after code execution?▼

Automated commits fail after code execution when parallel review gates, including code conventions, semantic clarity, or functional validation, detect issues that block the commit process.