step-commit

Capture per-step validated work as discrete commits in Code-Conductor.

3|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/Grimblaz/agent-orchestra --skill step-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: step-commit
Source: https://github.com/Grimblaz/agent-orchestra/tree/main/skills/step-commit
Command: npx skills add https://github.com/Grimblaz/agent-orchestra --skill step-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discrete validated-step commit workflow for Code-Conductor. Used to capture per-step validated work as structured commits, preserving traceability across the implementation loop while avoiding PR-time formatting gates.

Core Features & Use Cases

  • Opt-out control: respects the auto_commit_enabled flag to enable/disable step commits.
  • Branch safety: guards against commits on protected branches and prevents accidental changes.
  • Fine-grained file capture: detects changed files and stages only the intended ones for the step commit.
  • Standardized messages: creates commit messages that include step number, plan reference, involved agents, and validation tier.
  • Failure handling: escalates after consecutive failures and provides guardrails to recover gracefully.
  • Platform hooks: supports Claude Code and Copilot platforms for guided interactions when escalation is needed.

Quick Start

Trigger a step commit within Code-Conductor for the current step and verify the commit metadata is recorded.

Frequently Asked Questions about step-commit

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

FAQPage Schema
How do I automate git commits for validated workflow steps without breaking branch safety?

Selective file staging targets only intended changes for each step commit, preventing unrelated files from entering the workflow. It detects changed files and explicitly stages them, maintaining clean, discrete commits across the implementation loop.

What is the best way to structure git commit messages for automated workflow steps?

Opt-out control uses the auto_commit_enabled flag to disable step commits entirely. When toggled off, the workflow bypasses all automated commit actions, giving developers manual control over the version control process.

Does step-commit work with Claude Code and Copilot platforms for guided interactions?

Step-commit supports platform hooks for Claude Code and Copilot to enable guided interactions during failure escalation. When consecutive commit failures occur, these hooks provide guardrails to recover gracefully within the supported platforms.

How do I handle consecutive commit failures during an automated version control loop?

Failure handling escalates after consecutive commit failures and provides guardrails to recover gracefully. It leverages platform-specific hooks for Claude Code and Copilot to guide interactions, ensuring the workflow can resume safely.