version-chaos-untangler
Untangle a document that exists in six copies across email, drives, and desktops — establish the canonical version defensibly, merge the divergent edits, and install the single-source rule that prevents the rematch. Use when asked which version is the real one, merge these document copies, we've been editing different files, or stop the version chaos on this doc. Produces the version census with the canonical verdict, the divergence merge plan, the announce-and-redirect step, and the single-source going-forward rules.
npx skills add mohitagw15856/pm-claude-skills --skill version-chaos-untangler --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Version Chaos Untangler Skill Six copies of the contract: email attachments, two drives, someone's desktop, one renamed `-final-JT-edits`. Two have diverged — different edits on a shared ancestor — and the team is now editing in parallel universes. Untangling is forensic then structural: census every copy (where, modified-when, by-whom), establish the canonical *defensibly* (newest is not automatically rightest), merge what diverged, then kill the conditions — one home, links-not-attachments, and platform version history doing what filename suffixes failed to do. ## What This Skill Produces - **The version census** — every known copy: location, modified date, editor, size/diff signals - **The canonical verdict** — which version wins and *why* (the lineage argument, not just the timestamp) - **The merge plan** — the divergent edits reconciled, with the who-confirms list for judgment conflicts - **The single-source install** — one home, the redirect of every old copy, and the links-only norm ## Required Inputs Ask for these if not provided: - **The copies** — everywhere it lives (search email attachments by filename, both drives, ask the usual suspects); the census is only as good
- What This Skill Produces
- Required Inputs
- Framework: The Untangle Rules
- Output Format
- The Census
- The Verdict
- The Merge (if diverged)
- The Install
- Quality Checks
- Anti-Patterns
What does the version-chaos-untangler skill do?
Untangle a document that exists in six copies across email, drives, and desktops — establish the canonical version defensibly, merge the divergent edits, and install the single-source rule that prevents the rematch. Use when asked which version is the real one, merge these document copies, we've been editing different files, or stop the version chaos on this doc. Produces the version census with the canonical verdict, the divergence merge plan, the announce-and-redirect step, and the single-source going-forward rules.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill version-chaos-untangler --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 mohitagw15856/pm-claude-skills, a repository with 1,255 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.