sync-from-vibe-workflow

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
User request: $ARGUMENTS
Sync skills from the source vibe-workflow (in claude-code-plugins) to this codex-workflow repository, adapting Claude Code features to Codex equivalents.
用户请求:$ARGUMENTS
将claude-code-plugins中源vibe-workflow的skills同步至当前codex-workflow仓库,将Claude Code功能适配为Codex等效功能。

Phase 1: Setup & Discovery

第一阶段:准备与发现

1.1 Clone Source Repository

1.1 克隆源仓库

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
bash
git clone https://github.com/doodledood/claude-code-plugins /tmp/claude-code-plugins
若仓库已存在,拉取最新版本:
bash
cd /tmp/claude-code-plugins && git pull

1.2 List Skills and Agents

1.2 列出Skills与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
  3. 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.
源端位置:
  • Skills:
    /tmp/claude-code-plugins/claude-plugins/vibe-workflow/skills/
  • Agents:
    /tmp/claude-code-plugins/claude-plugins/vibe-workflow/agents/
目标端位置:
./skills/
列出目录名称与agent文件(不包含文件内容):
bash
ls /tmp/claude-code-plugins/claude-plugins/vibe-workflow/skills/
ls /tmp/claude-code-plugins/claude-plugins/vibe-workflow/agents/
ls ./skills/
Agent与Skill匹配:源端agents包含完整实现。通过以下方式动态匹配agents与目标端skills:
  1. 读取每个agent文件的前置元数据 - 提取
    name
    字段
  2. 在目标端skills中搜索匹配用途:
    • Agent
      code-X-reviewer
      → 查找
      review-X
      skill
    • Agent
      X-reviewer
      → 查找
      review-X
      skill
    • Agent
      X-fixer
      → 查找对应的修复skill(如
      bugfix
    • Agent名称可能不完全匹配 - 对比描述与用途
  3. 对于未匹配的agents - 确认是否需要创建新skill
注意:源端skills通常仅包含简短委托内容,如“使用X agent来...”。实际实现位于对应的agent文件中。同步时,请对比agent文件(而非简短的skill文件)与目标端skill。

1.3 Categorize Skills

1.3 对Skills进行分类

Compare the two lists and categorize:
CategoryCriteriaExample
ADDExists in source, not in destinationNew skill from upstream
MODIFYExists in both locationsExisting skill to sync
REMOVEExists only in destinationOrphaned 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
对比两个列表并分类:
类别判定标准示例
新增存在于源端,不存在于目标端来自上游的新技能
修改在两端均存在需要同步的现有技能
移除仅存在于目标端孤立技能(需询问用户)
特殊映射(尽管名称不同,仍视为修改类):
  • 源端
    implement-inplace
    → 目标端
    implement
  • 源端
    review-claude-md-adherence
    → 目标端
    review-agents-md-adherence

1.4 Create Todo List

1.4 创建待办事项列表

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
基于分类结果创建结构化待办事项:
[ ] 克隆/更新源仓库
[ ] 列出并分类skills
每个需新增的skill:
[ ] 新增{skill-name}: 从源端复制并适配
每个需修改的skill(每个skill对应两个待办):
[ ] 查看{skill-name}: 对比源端与目标端内容
[ ] 更新{skill-name}: 如有需要则应用变更
需移除的skill(经用户确认后):
[ ] 移除{skill-name}: 从目标端删除
最终步骤:
[ ] 若有skills新增/移除,更新README
[ ] 提交并推送变更
待办事项示例:
[x] 克隆/更新源仓库
[x] 列出并分类skills
[ ] 查看bugfix: 对比源端与目标端内容
[ ] 更新bugfix: 如有需要则应用变更
[ ] 查看plan: 对比源端与目标端内容
[ ] 更新plan: 如有需要则应用变更
[ ] 新增new-skill: 从源端复制并适配
[ ] 若有skills新增/移除,更新README
[ ] 提交并推送变更

Phase 2: Adaptation Rules

第二阶段:适配规则

When syncing skills, apply these transformations:
同步skills时,需应用以下转换规则:

2.1 Tool Mappings

2.1 工具映射

Claude CodeCodex Equivalent
TodoWrite
update_plan
Task(subagent)
N/A - inline execution only
Skill("vibe-workflow:skill-name")
$skill-name
AskUserQuestion
Standard user prompts
Claude CodeCodex等效工具
TodoWrite
update_plan
Task(subagent)
不适用 - 仅支持内联执行
Skill("vibe-workflow:skill-name")
$skill-name
AskUserQuestion
标准用户提示

2.2 File Reference Changes

2.2 文件引用变更

Claude CodeCodex
CLAUDE.md
AGENTS.md
/claude-code-plugins/...
Local paths
Claude CodeCodex
CLAUDE.md
AGENTS.md
/claude-code-plugins/...
本地路径

2.3 Special Cases

2.3 特殊情况

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
.
implement:由于Codex不支持子agents,此处的
implement
应与源端的
implement-inplace
保持一致(而非使用子agents的编排器
implement
)。
review-claude-md-adherence:映射至
review-agents-md-adherence
- 将所有引用从
CLAUDE.md
更新为
AGENTS.md

2.4 Skill Format

2.4 Skill格式

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
源端使用Claude Code skill格式。目标端使用Codex格式:
yaml
---
name: skill-name
description: "描述不超过500字符,包含触发条件。"
---

Skill说明...
限制:
  • name
    : 最多100字符
  • description
    : 最多500字符

Phase 3: Sync Process

第三阶段:同步流程

3.1 For Skills to ADD

3.1 新增Skills

  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/<skill-name> ./skills/
  3. Read the copied SKILL.md
  4. Apply adaptation rules from Phase 2
  5. Write adapted skill
  6. Mark todo
    completed
  1. 将“新增{skill-name}”待办标记为
    in_progress
  2. 从源端复制skill目录:
    bash
    cp -r /tmp/claude-code-plugins/claude-plugins/vibe-workflow/skills/<skill-name> ./skills/
  3. 读取复制后的SKILL.md
  4. 应用第二阶段的适配规则
  5. 写入适配后的skill
  6. 将待办标记为
    completed

3.2 For Skills to MODIFY (Two-Step Process)

3.2 修改Skills(两步流程)

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
  3. Read source (agent or skill based on above)
  4. Read destination:
    ./skills/{skill-name}/SKILL.md
  5. 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)
  6. Note findings (what needs updating, what's already correct)
  7. 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)
  4. Mark todo
    completed
第一步:读取与对比
  1. 将“查看{skill-name}”待办标记为
    in_progress
  2. 确定事实来源:
    • 检查源端skill是否为简短委托(如“使用X agent来...”)
    • 若是简短委托 → 读取对应的agent文件作为源端内容
    • 若是完整实现 → 读取skill文件作为源端内容
  3. 读取源端内容(根据上述规则选择agent或skill文件)
  4. 读取目标端内容:
    ./skills/{skill-name}/SKILL.md
  5. 识别差异:
    • 源端中需要同步的内容变更
    • 目标端中需保留的Codex特定适配
    • 已保持同步的部分(无需变更)
  6. 记录发现结果(需要更新的内容、已正确的内容)
  7. 将待办标记为
    completed
第二步:更新
  1. 将“更新{skill-name}”待办标记为
    in_progress
  2. 若无需变更 → 标记为
    completed
    ,继续处理下一个
  3. 若需要变更:
    • 应用源端变更的同时保留Codex适配
    • 使用编辑工具进行针对性更新(而非完全重写)
    • 确保目标端skill包含完整实现(而非简短委托)
  4. 将待办标记为
    completed

3.2.1 Agent-to-Skill Sync Pattern

3.2.1 Agent至Skill同步模式

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
  4. Apply updates from agent to skill:
    • New sections, categories, or guidelines from the agent
    • Updated review processes or criteria
    • New output formats or examples
  5. Preserve Codex adaptations:
    • AGENTS.md
      instead of
      CLAUDE.md
    • $skill-name
      invocation format
    • No subagent references
    • Codex frontmatter format
将agent同步至skill时:
  1. 读取源端agent文件(如
    agents/code-bugs-reviewer.md
  2. 读取目标端skill文件(如
    skills/review-bugs/SKILL.md
  3. 对比内容 - 目标端应包含:
    • 正确的Codex前置元数据(
      name
      ,
      description
      ,
      metadata
    • 从agent适配而来的完整Codex实现
  4. 将agent的更新应用至skill:
    • agent中的新章节、分类或指南
    • 更新后的评审流程或标准
    • 新的输出格式或示例
  5. 保留Codex适配:
    • 使用
      AGENTS.md
      而非
      CLAUDE.md
    • 使用
      $skill-name
      调用格式
    • 无subagent引用
    • Codex前置元数据格式

3.3 For Skills to REMOVE

3.3 移除Skills

  1. Ask user for confirmation before removing
  2. If confirmed, delete skill directory
  3. Note removal for README update
  1. 移除前需询问用户确认
  2. 若确认,删除skill目录
  3. 记录移除操作以便更新README

3.4 Preserve Codex-Specific Content

3.4 保留Codex特定内容

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)
更新时需保留:
  • AGENTS.md
    引用(不要恢复为
    CLAUDE.md
  • update_plan
    (不要恢复为
    TodoWrite
  • $skill-name
    调用格式
  • 内联执行模式(不要添加subagent引用)
  • 扩展实现(目标端可能比源端的简短委托更完整)

Phase 4: Finalize

第四阶段:最终收尾

4.1 Update README

4.1 更新README

If skills were added or removed, update
README.md
:
  • Available Skills section
  • Repository Structure (if directories changed)
若有skills新增或移除,更新
README.md
:
  • 可用Skills章节
  • 仓库结构(若目录有变更)

4.2 Commit Changes

4.2 提交变更

For each logical group of changes:
bash
git add <files>
git commit -m "Sync <skill-name> from vibe-workflow"
Or batch commit:
bash
git add skills/
git commit -m "Sync skills from vibe-workflow"
针对每个逻辑变更组:
bash
git add <files>
git commit -m "Sync <skill-name> from vibe-workflow"
或批量提交:
bash
git add skills/
git commit -m "Sync skills from vibe-workflow"

4.3 Push

4.3 推送

bash
git push -u origin <branch>
bash
git push -u origin <branch>

Edge Cases

边缘情况

CaseAction
Skill exists only in destinationAsk user before removing
Skill renamed in sourceCreate new, ask about removing old
Major structural changesDocument changes, proceed with sync
Source skill uses subagentsAdapt to inline execution (run sequentially)
Source skill is brief delegationRead the corresponding agent file as the source of truth
Source agent updated but dest skill existsSync agent changes into the destination skill
Conflicting contentPrefer source logic, apply Codex adaptations
情况处理方式
Skill仅存在于目标端移除前询问用户
Skill在源端重命名创建新skill,询问是否移除旧skill
重大结构变更记录变更,继续同步
源端Skill使用subagents适配为内联执行(按顺序运行)
源端Skill为简短委托读取对应的agent文件作为事实来源
源端Agent更新但目标端Skill已存在将agent变更同步至目标端skill
内容冲突优先采用源端逻辑,应用Codex适配

Verification Checklist

验证清单

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
同步完成后,验证以下内容:
  • 所有
    Skill("vibe-workflow:...")
    调用已转换为
    $skill-name
  • 所有
    TodoWrite
    引用已转换为
    update_plan
  • 所有
    CLAUDE.md
    引用已转换为
    AGENTS.md
  • 无剩余subagent Task()调用
  • 无剩余AskUserQuestion工具引用
  • 描述不超过500字符
  • 名称不超过100字符

Source Reference

源端参考