ralph-run-reconcile-codex

Audit and reconcile the latest Ralph run for unmerged branches, failures, drift, and merge issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the post-execution gaps and potential issues that can arise after an automated ralph run, ensuring the integrity and completeness of the development process.

Core Features & Use Cases

  • Post-Run Auditing: Detects unmerged branches, failures, state/spec drift, and merge conflicts.
  • Bounded Remediation: Applies a structured recovery plan with varying levels of automation based on risk.
  • Use Case: After a long ralph run completes, use this Skill to automatically check for any lingering issues like orphaned branches or inconsistencies in the state file, and then safely clean them up.

Quick Start

Run the ralph-run-reconcile-codex skill to report on the status of the last Ralph run.

Frequently Asked Questions about ralph-run-reconcile-codex

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

FAQPage Schema
How do I detect unmerged story branches after an automated git run?

To detect unmerged story branches after an automated git run, the ralph-run-reconcile-codex skill audits the latest execution in Codex-driven repositories. It identifies orphaned branches, execution failures, and merge conflicts to ensure process integrity and completeness.

What is spec drift in automated code review workflows and how do I check for it?

Spec drift in automated code review workflows occurs when repository state diverges from defined specifications. The ralph-run-reconcile-codex skill checks for this drift during its post-run audit, detecting inconsistencies between the actual code state and the expected specifications.

How do I safely clean up orphaned branches and state file inconsistencies after a ralph run?

To safely clean up orphaned branches and state file inconsistencies after a ralph run, you can use the bounded recovery plan provided by this skill. It offers configurable operating modes for reporting, safe execution, or approved execution of remediation actions based on risk.

Does the ralph-run-reconcile-codex skill require additional dependencies to audit repositories?

No, the ralph-run-reconcile-codex skill does not require additional dependencies to audit repositories. It operates independently to detect state drift and merge issues, executing its bounded recovery plan directly within Codex-driven environments without external modules.

What is the best way to reconcile post-execution gaps and merge issues in Codex-driven repositories?

The best way to reconcile post-execution gaps and merge issues in Codex-driven repositories is to run a structured recovery plan. This skill audits the latest run and applies bounded remediation with varying levels of automation based on the specific risk involved.