ralph-run-reconcile-claude-code

Audit Ralph runs to detect missing merges, state drift, and run failures.

4|1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/becerra-alberto/ralphetamine --skill ralph-run-reconcile-claude-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-run-reconcile-claude-code
Source: https://github.com/becerra-alberto/ralphetamine/tree/main/skills/ralph-run-reconcile-claude-code
Command: npx skills add https://github.com/becerra-alberto/ralphetamine --skill ralph-run-reconcile-claude-code

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the potential for drift and inconsistencies after an automated coding run by Ralph, ensuring that the implemented code aligns with the intended state and that no merges or changes are missed.

Core Features & Use Cases

  • Audit Ralph Runs: Inspect story branches, state/spec drift, and merge conflicts.
  • Prioritize Fixes: Produce or execute a prioritized remediation plan for failures or tentative outcomes.
  • Use Case: After a ralph run completes with several failures, use this Skill to systematically identify the root causes, such as unmerged commits or state mismatches, and generate a clear plan to fix them.

Quick Start

Use the ralph-run-reconcile-claude-code skill to audit the last Ralph run and produce an execution plan.

Frequently Asked Questions about ralph-run-reconcile-claude-code

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

FAQPage Schema
How do I reconcile code drift after an automated coding run?

To reconcile code drift after an automated coding run, audit story branches, state mismatches, and merge conflicts to produce a prioritized remediation plan for the affected repository.

What causes missing merges and state drift in Claude Code?

State drift and missing merges in Claude Code are caused by inconsistencies after an automated run, which requires deterministic checks on story branches to detect unmerged commits and spec mismatches.

How do I generate a remediation plan for failed code review runs?

Generate a remediation plan for failed code review runs by inspecting story branches and merge conflicts, applying a risk-based approach to prioritize fixes for detected run failures.

Can I execute fixes automatically when debugging reconciliation errors?

Yes, you can execute fixes automatically when debugging reconciliation errors by applying a risk-based approach to the prioritized remediation plan generated from the audit findings.

Does this reconciliation process require deterministic checks for merge conflicts?

Yes, the reconciliation process requires deterministic checks to accurately detect merge conflicts, state drift, and missing merges, ensuring a risk-based approach to applying fixes.

What is the best way to audit story branches for spec mismatches?

The best way to audit story branches for spec mismatches is to run a reconciliation process that inspects branches for state drift and generates a prioritized remediation plan based on the findings.