implement-commit

Execute commits from TOML implementation plans via a deterministic TDD pipeline.

5|12|Updated Nov 24, 2025

Search Tags:#automation #TDD #gates #dependency-graph #style-review #commit-pipeline #phase-isolation

Ready to run

npx skills add https://github.com/cbgbt/bottlerocket-forest --skill implement-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement-commit
Source: https://github.com/cbgbt/bottlerocket-forest/tree/main/skills/implement-commit
Command: npx skills add https://github.com/cbgbt/bottlerocket-forest --skill implement-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates the automated execution of commits from a feature's implementation plan, reducing manual toil and ensuring consistency via a deterministic TDD pipeline.

Core Features & Use Cases

Plan-driven commit orchestration: Converts an implementation-plan.toml into a sequence of commits with dependency resolution.
Phased execution: Runs Designer, Tester, Implementor, Arbiter, and Scope phases with gate and formatters checks and ledger logging.
Use Case: When refining a feature, execute all required commits in dependency order and consolidate results with style reviews and scope checks.

Quick Start

Use the implement-commit skill to process an implementation plan at docs/features/NNNN-name/implementation-plan.toml and produce ready commits in the workspace.

Frequently Asked Questions about implement-commit

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

FAQPage Schema

How do I automate TDD commits from an implementation plan?▼

To automate TDD commits from an implementation plan, this Skill parses a TOML plan and orchestrates Designer, Tester, Implementor, Arbiter, and Scope phases to execute commits in dependency order with gate and formatter checks.

What is a deterministic commit pipeline for feature implementation?▼

A deterministic commit pipeline processes implementation plans by resolving dependencies, applying style reviews, and logging progress in a ledger to ensure consistent, automated feature commits through isolated TDD phases.

Do I need an implementation-plan.toml file to run automated commits?▼

Yes, you need an implementation-plan.toml file located at docs/features/NNNN-name/ to run automated commits, as the pipeline parses this file to manage dependency resolution and orchestrate the required TDD phases.

Can I run style reviews and scope checks automatically during commit execution?▼

Yes, you can run style reviews and scope checks automatically during commit execution, as the pipeline applies gate and formatter checks while orchestrating the Implementor and Arbiter phases to consolidate results.

What's the best way to manage dependency resolution for feature commits?▼

The best way to manage dependency resolution for feature commits is using a plan-driven pipeline that parses TOML files to sequence commits based on dependencies and logs progress in a ledger.

Why does commit automation isolate execution into separate phases?▼

Commit automation isolates execution into separate Designer, Tester, Implementor, Arbiter, and Scope phases to enforce deterministic TDD gates, ensuring style reviews and dependency resolution are consistently validated before logging progress.