How do I install the Etanhey Golems Commit skill?

Run npx skillmds@latest add tomevault-io/etanhey-golems-commit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Etanhey Golems Commit skill do?

Commit with Code Review It is listed under Coding & Dev Tools on SkillMD.

Is Etanhey Golems Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Etanhey Golems Commit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Etanhey Golems Commit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Etanhey Golems Commit?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Etanhey Golems Commit by tomevault-io

Name: Etanhey Golems Commit
Author: tomevault-io

File contents

Commit with Code Review

Runs CodeRabbit review on staged changes, then commits if approved.

Flow

Check for staged changes
Run CodeRabbit review (cr review --plain for headless/Claude compatibility)
Show review results
If review passes → prompt for commit message → commit
If review fails → show issues → ask user if they want to proceed anyway

Usage

# Stage your changes first
git add <files>

# Standard commit
/commit

# Ralph mode — atomic commit + mark story criterion
/commit --story=US-106 --message="feat: US-106 description"

What This Skill Does

When invoked, Claude will:

Check staged changes: Run git diff --staged --stat to show what's staged
Run CodeRabbit: Execute cr review --plain (headless mode, works from Claude)
Evaluate results:
- If CR passes (no critical issues): proceed to commit
- If CR fails: show issues and ask user for decision
Commit: Generate commit message based on changes, commit with co-author

Ralph Mode (Story Commits)

When --story is provided, this skill does atomic commit + criterion marking:

Stages files (specified or auto-detected)
Commits (pre-commit hook runs all tests)
If commit succeeds → marks the commit criterion as checked in story JSON
If commit fails → neither happens, reports failure

Ralph Mode Flags

Flag	Description
`--story=ID`	Story ID (e.g., US-106, BUG-028) — triggers Ralph mode
`--message=MSG`	Commit message (required in Ralph mode)
`--files=PATHS`	Files to stage (default: prd-json/ + modified files)
`--dry-run`	Show what would happen without doing it

Why Ralph Mode Exists

Atomic: Either both happen (commit + check) or neither
No double-testing: Uses pre-commit hook, doesn't run tests twice
Clean failure: If tests fail, criterion stays unchecked for retry

Requirements

cr CLI installed (CodeRabbit)
Changes staged with git add

After Committing

Committing is ONE step in the full workflow. After commit:

Push → git push -u origin <branch>
PR + Review + Merge → /pr-loop (the full loop)

Do NOT stop at commit. The mission is MERGED, not committed.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: etanhey-golems-commitdescription: Commit with Code Review---# Commit with Code ReviewRuns CodeRabbit review on staged changes, then commits if approved.## Flow1. Check for staged changes2. Run CodeRabbit review (`cr review --plain` for headless/Claude compatibility)3. Show review results4. If review passes → prompt for commit message → commit5. If review fails → show issues → ask user if they want to proceed anyway## Usage```bash# Stage your changes firstgit add <files># Standard commit/commit# Ralph mode — atomic commit + mark story criterion/commit --story=US-106 --message="feat: US-106 description"```## What This Skill DoesWhen invoked, Claude will:1. **Check staged changes**: Run `git diff --staged --stat` to show what's staged2. **Run CodeRabbit**: Execute `cr review --plain` (headless mode, works from Claude)3. **Evaluate results**: - If CR passes (no critical issues): proceed to commit - If CR fails: show issues and ask user for decision4. **Commit**: Generate commit message based on changes, commit with co-author## Ralph Mode (Story Commits)When `--story` is provided, this skill does atomic commit + criterion marking:1. **Stages files** (specified or auto-detected)2. **Commits** (pre-commit hook runs all tests)3. **If commit succeeds** → marks the commit criterion as checked in story JSON4. **If commit fails** → neither happens, reports failure### Ralph Mode Flags| Flag | Description ||------|-------------|| `--story=ID` | Story ID (e.g., US-106, BUG-028) — triggers Ralph mode || `--message=MSG` | Commit message (required in Ralph mode) || `--files=PATHS` | Files to stage (default: prd-json/ + modified files) || `--dry-run` | Show what would happen without doing it |### Why Ralph Mode Exists- **Atomic**: Either both happen (commit + check) or neither- **No double-testing**: Uses pre-commit hook, doesn't run tests twice- **Clean failure**: If tests fail, criterion stays unchecked for retry## Requirements- `cr` CLI installed (CodeRabbit)- Changes staged with `git add`## After CommittingCommitting is ONE step in the full workflow. After commit:1. **Push** → `git push -u origin <branch>`2. **PR + Review + Merge** → `/pr-loop` (the full loop)**Do NOT stop at commit.** The mission is MERGED, not committed.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/etanhey) — claim your Tome and manage your conversions.

Frequently asked questions

Etanhey Golems Commit