ralph-commit

Create structured git commits with decisions, files, and blockers.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/danievanzyl/code-skills --skill ralph-commit-danievanzyl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ralph-commit
Source: https://github.com/danievanzyl/code-skills/tree/main/skills/ralph-commit
Command: npx skills add https://github.com/danievanzyl/code-skills --skill ralph-commit-danievanzyl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Make a git commit that captures key decisions, files changed, and blockers/notes for the next iteration, ensuring traceability in Ralph-style loops.

Core Features & Use Cases

  • Structured commit bodies with sections for Decisions, Files, and Blockers to keep iteration context clear.
  • Derives a concise subject from the changes or uses a user-provided one to maintain readable history.
  • Guards against exposing secrets and validates repository state before performing the commit.

Quick Start

Provide an optional subject and let the tool generate a structured commit message for the next iteration.

Frequently Asked Questions about ralph-commit

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

FAQPage Schema
How do I document decisions and blockers in a git commit?▼

To document decisions and blockers in a git commit, you use a structured template that separates the message into sections for decisions, files changed, and blockers, ensuring iteration traceability.

What is a structured git commit template for iteration tracking?▼

A structured git commit template organizes iteration context by generating a commit body with dedicated sections for Decisions, Files, and Blockers, while deriving a concise subject from your changes.

How do I create git commits that capture iteration context across multiple files?▼

You capture iteration context across multiple files by applying a predefined commit format that validates repository state, prompts for missing context, and documents decisions alongside files changed.

Does this structured commit tool check for secrets before committing?▼

Yes, the structured commit tool guards against exposing secrets and validates the repository state before performing the git commit to ensure safe iteration tracking.

Do I need to provide a commit subject manually?▼

You do not need to provide a commit subject manually; the tool derives a concise subject from your changes automatically, though you can supply an optional user-provided subject.

What happens if context is missing during a structured git commit?▼

If context is missing during a structured git commit, the tool prompts you to provide the necessary details so it can accurately format the decisions and blockers for the iteration.