Install the helpers

The Corotation installer can add a small conflict skill to Codex, Claude, or both. The skill explains how to inspect conflict state, preserve competing versions, and perform an authorized repair. 

cor install --skills both
cor install --skills both --project

Choices are both, codex, claude, and none. Customized existing skills are preserved on reinstall.

Where skills live

Agent Project installation Personal installation
Codex .agents/skills/corotation-conflicts/ ~/.agents/skills/corotation-conflicts/
Claude .claude/skills/corotation-conflicts/ ~/.claude/skills/corotation-conflicts/

Claude’s personal location respects CLAUDE_CONFIG_DIR when configured. Refer to the official Codex skill guide and Claude skill guide for how each agent discovers skills.

What to ask your agent

While the agent is working on the project, ask it to inspect conflicts or keep an eye on them during the task. For example: 

Use the corotation-conflicts skill while working on this task.
Monitor conflicts and adjust your edits to the latest current,
keeping the task’s intended behavior and preserving both versions.
Resolve clear conflicts, restart sync, and verify the result.
Ask me when the intended result is ambiguous.

The helper uses cor status --json to inspect worker and conflict state without contacting current. For an ongoing watch during an active task, it can run: 

cor conflicts --watch --json

What the skill does not do

A skill is guidance for an active agent

Installing it does not start an AI daemon, schedule notifications, or wake an inactive agent. A monitoring process lasts only while someone keeps it running.

The helper should report affected packages and paths, inspect preserved copies, and follow your instructions for the desired repair. It should not delete the conflict report or automatically choose a version just to clear a warning.

Repair workflow

For publication check failures, monitor cor checks --watch --json. Repair the working files and save while cor work stays running. Validation automatically retries and publishes the complete package when it passes. The helper must not weaken the checks or approve a changed policy to clear a failure. Use cor hold and cor resume for an intermediate refactor that must stay private.

Resolution affects all active conflict packages. The agent must inspect that scope, stop the workspace’s worker, preserve recovery archives, and then use cor resolve --take local or --take current according to the intended result.

Restart cor work after the repair and verify with cor status --json. A concurrent edit can reject a repaired package again; that new conflict needs inspection, not an endless automatic retry.