sync-from-vibe-workflow

1.1 Clone Source Repository

```bash

git clone https://github.com/doodledood/claude-code-plugins /tmp/claude-code-plugins

```

If already exists, pull latest:

```bash

cd /tmp/claude-code-plugins && git pull

```

1.2 List Skills and Agents

Source locations:

• Skills: /tmp/claude-code-plugins/claude-plugins/vibe-workflow/skills/
• Agents: /tmp/claude-code-plugins/claude-plugins/vibe-workflow/agents/

Destination location: ./skills/

List directory names and agent files (NOT file contents):

```bash

ls /tmp/claude-code-plugins/claude-plugins/vibe-workflow/skills/

ls /tmp/claude-code-plugins/claude-plugins/vibe-workflow/agents/

ls ./skills/

```

Agent-to-Skill Discovery: Source agents contain full implementations. Dynamically match agents to destination skills by:

1. Read each agent file's frontmatter - extract the name field
2. Search destination skills for matching purpose:

- Agent code-X-reviewer → look for review-X skill

- Agent X-reviewer → look for review-X skill

- Agent X-fixer → look for corresponding fix skill (e.g., bugfix)

- Agent names may not match exactly - compare descriptions and purpose

1. For unmatched agents - check if a new skill should be created

Note: Source skills often have brief delegations like "Use the X agent to...". The actual implementation is in the corresponding agent file. When syncing, compare the agent file (not the brief skill) against the destination skill.

1.3 Categorize Skills

Compare the two lists and categorize:

| Category | Criteria | Example |

|----------|----------|---------|

| ADD | Exists in source, not in destination | New skill from upstream |

| MODIFY | Exists in both locations | Existing skill to sync |

| REMOVE | Exists only in destination | Orphaned skill (ask user) |

Special mappings (treat as MODIFY despite name difference):

• Source implement-inplace → Destination implement
• Source review-claude-md-adherence → Destination review-agents-md-adherence

1.4 Create Todo List

Create structured todos based on categorization:

```

[ ] Clone/update source repository

[ ] List and categorize skills

```

For each skill to ADD:

```

[ ] Add {skill-name}: copy from source and adapt

```

For each skill to MODIFY (TWO todos per skill):

```

[ ] Read {skill-name}: compare source and destination

[ ] Update {skill-name}: apply changes if needed

```

For skills to REMOVE (after user confirmation):

```

[ ] Remove {skill-name}: delete from destination

```

Finalization:

```

[ ] Update README if skills added/removed

[ ] Commit and push changes

```

Example todo list:

```

[x] Clone/update source repository

[x] List and categorize skills

[ ] Read bugfix: compare source and destination

[ ] Update bugfix: apply changes if needed

[ ] Read plan: compare source and destination

[ ] Update plan: apply changes if needed

[ ] Add new-skill: copy from source and adapt

[ ] Update README if skills added/removed

[ ] Commit and push changes

```

When syncing skills, apply these transformations:

2.1 Tool Mappings

| Claude Code | Codex Equivalent |

|-------------|------------------|

| TodoWrite | update_plan |

| Task(subagent) | N/A - inline execution only |

| Skill("vibe-workflow:skill-name") | $skill-name |

| AskUserQuestion | Standard user prompts |

2.2 File Reference Changes

| Claude Code | Codex |

|-------------|-------|

| CLAUDE.md | AGENTS.md |

| /claude-code-plugins/... | Local paths |

2.3 Special Cases

implement: Since Codex has no subagents, implement here should match implement-inplace from source (not the orchestrator implement that uses subagents).

review-claude-md-adherence: Maps to review-agents-md-adherence - update all references from CLAUDE.md to AGENTS.md.

2.4 Skill Format

Source uses Claude Code skill format. Destination uses Codex format:

```yaml

---

name: skill-name

description: "Description under 500 chars. Include triggers."

---

Skill instructions...

```

Limits:

• name: max 100 characters
• description: max 500 characters

3.1 For Skills to ADD

1. Mark "Add {skill-name}" todo as in_progress
2. Copy skill directory from source:

```bash

cp -r /tmp/claude-code-plugins/claude-plugins/vibe-workflow/skills/ ./skills/

```

1. Read the copied SKILL.md
2. Apply adaptation rules from Phase 2
3. Write adapted skill
4. Mark todo completed

3.2 For Skills to MODIFY (Two-Step Process)

Step 1: Read and Compare

1. Mark "Read {skill-name}" todo as in_progress
2. Determine the source of truth:

- Check if source skill is a brief delegation (e.g., "Use the X agent to...")

- If brief delegation → read the corresponding agent file as the source

- If full implementation → read the skill file as source

1. Read source (agent or skill based on above)
2. Read destination: ./skills/{skill-name}/SKILL.md
3. Identify differences:

- Content changes in source that should be synced

- Codex-specific adaptations in destination to preserve

- Already up-to-date sections (no change needed)

1. Note findings (what needs updating, what's already correct)
2. Mark todo completed

Step 2: Update

1. Mark "Update {skill-name}" todo as in_progress
2. If no changes needed → mark completed, move on
3. If changes needed:

- Apply source changes while preserving Codex adaptations

- Use Edit tool for targeted updates (not full rewrites)

- Ensure the destination skill has the FULL implementation (not a brief delegation)

1. Mark todo completed

3.2.1 Agent-to-Skill Sync Pattern

When syncing an agent to a skill:

1. Read the source agent file (e.g., agents/code-bugs-reviewer.md)
2. Read the destination skill file (e.g., skills/review-bugs/SKILL.md)
3. Compare content - the destination should contain:

- Proper Codex frontmatter (name, description, metadata)

- Full implementation from the agent, adapted for Codex

1. Apply updates from agent to skill:

- New sections, categories, or guidelines from the agent

- Updated review processes or criteria

- New output formats or examples

1. Preserve Codex adaptations:

- AGENTS.md instead of CLAUDE.md

- $skill-name invocation format

- No subagent references

- Codex frontmatter format

3.3 For Skills to REMOVE

1. Ask user for confirmation before removing
2. If confirmed, delete skill directory
3. Note removal for README update

3.4 Preserve Codex-Specific Content

When updating, preserve:

• AGENTS.md references (don't revert to CLAUDE.md)
• update_plan (don't revert to TodoWrite)
• $skill-name invocation format
• Inline execution patterns (don't add subagent references)
• Expanded implementations (destination may have fuller versions than source's brief delegations)

4.1 Update README

If skills were added or removed, update README.md:

• Available Skills section
• Repository Structure (if directories changed)

4.2 Commit Changes

For each logical group of changes:

```bash

git add

git commit -m "Sync from vibe-workflow"

```

Or batch commit:

```bash

git add skills/

git commit -m "Sync skills from vibe-workflow"

```

4.3 Push

```bash

git push -u origin

```

| Case | Action |

|------|--------|

| Skill exists only in destination | Ask user before removing |

| Skill renamed in source | Create new, ask about removing old |

| Major structural changes | Document changes, proceed with sync |

| Source skill uses subagents | Adapt to inline execution (run sequentially) |

| Source skill is brief delegation | Read the corresponding agent file as the source of truth |

| Source agent updated but dest skill exists | Sync agent changes into the destination skill |

| Conflicting content | Prefer source logic, apply Codex adaptations |

After sync, verify:

• [ ] All Skill("vibe-workflow:...") calls converted to $skill-name
• [ ] All TodoWrite references converted to update_plan
• [ ] All CLAUDE.md references converted to AGENTS.md
• [ ] No subagent Task() calls remain
• [ ] No AskUserQuestion tool references remain
• [ ] Description under 500 chars
• [ ] Name under 100 chars

• Source repo: https://github.com/doodledood/claude-code-plugins
• Source path: claude-plugins/vibe-workflow/skills/
• Note: vibe-workflow is the upstream/source of truth for skill logic