ca-conflict
Stop everything and surface a rule conflict — persona vs. docs vs. code. Present both sides and the conflict-hierarchy level; the user resolves. No silent reconciliation.
npx skills add arbiterForge/codeArbiter --skill ca-conflict --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# $ca-conflict — conflict protocol Orchestrator protocol, not a skill route. When a rule conflict surfaces — the persona, a `.codearbiter/` document, and code contradict each other, or two docs contradict each other — all other work STOPs and the conflict is presented for the user to resolve. The orchestrator never picks a side. ## Flow 1. **Halt** — suspend the in-progress task. No partial progress. 2. **Identify** the conflicting sources (A and B): which document, file, or rule each is. 3. **Quote** the exact passages side by side. 4. **Classify** the conflict against the §2 conflict-resolution hierarchy and name the level the tension sits at. Note which source was more recently updated — informational, not determinative. 5. **Present** and wait. Work resumes only after the user explicitly resolves. ## Output ``` ## Conflict detected — work halted ### Source A File: <path> · Last updated: <date> > <exact quoted text> ### Source B File: <path> · Last updated: <date> > <exact quoted text> ### Nature of conflict <what the two sources disagree about> ### Conflict-hierarchy level Level N — <why the tension sits here> ### To resolve <options — update A, update B, or supersede one via a
- Flow
- Output
- When routed automatically
- After resolution
- Hard gate
What does the ca-conflict skill do?
Stop everything and surface a rule conflict — persona vs. docs vs. code. Present both sides and the conflict-hierarchy level; the user resolves. No silent reconciliation.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill ca-conflict --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From arbiterForge/codeArbiter, a repository with 138 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.