forge-coder

Validate diffs, run per-group tests, and generate a coder-report.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/SirTheOracle/forge-toolkit --skill forge-coder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-coder
Source: https://github.com/SirTheOracle/forge-toolkit/tree/main/codex-skills/forge-coder
Command: npx skills add https://github.com/SirTheOracle/forge-toolkit --skill forge-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Procedural coding workflow that reads implementation.md, validates diffs against the codebase, applies changes in execution order, runs tests after each commit group, and produces a coder-report.md artifact.

Core Features & Use Cases

  • Reads implementation.md to derive the exact sequence of changes and enforcement rules.
  • Enforces pre-flight checks, per-group testing, and structured commits, while generating a complete coder-report.
  • Use Case: teams can automate safe code diffs across multiple commits with full traceability and reporting.

Quick Start

Run the forge-coder skill on a proposal directory (e.g., .dev/proposals/{slug}) to automatically validate, apply changes, and generate a coder-report.

Frequently Asked Questions about forge-coder

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

FAQPage Schema
How do I automate code validation and apply diffs across multiple commits?

To automate code validation, you can use a procedural workflow that reads implementation rules, applies diffs in execution order, and runs per-group tests before committing changes. This generates a detailed coder-report for full traceability.

What is a coder-report and how does it help with traceability?

A coder-report is an artifact generated after applying validated code changes. It records test outcomes, enforcement actions, and structured commit details, providing complete traceability for automated end-to-end code-change campaigns.

How do I enforce pre-flight checks and per-group testing before committing code?

You enforce pre-flight checks and per-group testing by orchestrating a procedural coding workflow that validates diffs against the repository. Changes are applied only after successful validation, ensuring structured commits.

Do I need an implementation.md file to run automated diff validation?

Yes, an implementation.md file is required. The workflow reads this file to derive the exact sequence of code changes, enforcement rules, and execution order needed to validate diffs and generate the coder-report.

Can I apply code changes in execution order and stop if tests fail?

Yes, the workflow applies code changes in execution order and runs tests after each commit group. It enforces safety constraints and only applies changes after successful validation, halting if tests fail.

What are the limitations of automating code-change campaigns with diff validation?

Limitations include strict dependency on a properly formatted implementation.md file for enforcement rules. The workflow requires tests to pass after each commit group, meaning any validation failure stops the automated code-change campaign.