/pace-sync
Use when user says "同步/sync/同步到GitHub/关联Issue/unlink/Gate同步/sub-issue/全量同步/增量同步" or /pace-sync. Syncs Epic/BR/PF/CR to GitHub Issues. NOT for internal state (use /pace-dev).
$ npx -y skills add arch-team/devpace --skill pace-sync --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/pace-sync
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when user says "同步/sync/同步到GitHub/关联Issue/unlink/Gate同步/sub-issue/全量同步/增量同步" or /pace-sync. Syncs Epic/BR/PF/CR to GitHub Issues. NOT for internal state (use /pace-dev).
SKILL.md
pace-sync.SKILL.mddescription: Use when user says "同步/sync/同步到GitHub/关联Issue/unlink/Gate同步/sub-issue/全量同步/增量同步" or /pace-sync. Syncs Epic/BR/PF/CR to GitHub Issues. NOT for internal state (use /pace-dev).
argument-hint: "[子命令] [参数]"
allowed-tools: AskUserQuestion, Read, Write, Edit, Glob, Grep, Bash
model: sonnet
/pace-sync — 外部工具同步
将 devpace 全部实体(Epic/BR/PF/CR)与外部项目管理工具同步。支持 GitHub(当前),设计为 Linear/Jira 可扩展。
与现有机制的关系
- /pace-dev 管理 CR 内部状态转换 → /pace-sync 将状态变化推送到外部
- /pace-change 管理变更操作 → /pace-sync 同步变更后状态到外部
- /pace-release 管理发布流程 → /pace-sync 同步发布状态到外部
- /pace-review Gate 2 结果 → /pace-sync Gate 结果自动推送(Comment + 标签)
- /pace-status 展示内部状态 → /pace-sync status 展示同步状态和外部链接
推荐使用流程
首次配置:`setup` → 日常同步:`/pace-sync`(智能同步)→ 查看状态:`status`
输入
`$ARGUMENTS` 解析为子命令 + 参数。
子命令
| 子命令 | 参数 | 说明 | |--------|------|------| | sync | [--dry-run] | **智能同步**(默认行为):自动检测变更,呈现摘要,确认后执行。无参数时等价。 | | link | 实体ID [#外部ID] | 关联实体与已有外部 Issue(支持 EPIC-xxx/BR-xxx/PF-xxx/CR-xxx;省略外部 ID 则智能匹配) | | unlink | 实体ID | 解除实体与外部的关联 | | status | [--all] | 查看同步状态(--all 显示全部实体类型,默认仅 CR) | | setup | [--auto] | 引导式同步配置(--auto 跳过交互确认) | | pull | 实体ID | 查询外部状态,提示用户是否更新 devpace(轻量检查) |
**无参数时默认执行智能同步(sync)。**
**实体 ID 格式**:`EPIC-001`、`BR-002`、`PF-003`、`CR-004`(前缀确定类型)。纯数字默认为 CR(向后兼容)。
流程
1. 读取 `.devpace/integrations/sync-mapping.md`(不存在 → 引导 `setup`) 2. 加载 `skills/pace-sync/sync-procedures-common.md`(始终加载) 3. **根据子命令,仅加载对应的 procedures 文件**(均位于 `skills/pace-sync/` 目录):
| 参数 | 加载文件 | |------|---------| | `sync` / (空) | skills/pace-sync/sync-procedures-entity.md(智能同步主流程) | | `sync --dry-run` | skills/pace-sync/sync-procedures-entity.md(dry-run 模式) | | `link` | skills/pace-sync/sync-procedures-link.md + skills/pace-sync/sync-procedures-entity.md(§1 ID 解析) | | `unlink` | skills/pace-sync/sync-procedures-status.md + skills/pace-sync/sync-procedures-entity.md(§1 ID 解析) | | `status` [--all] | skills/pace-sync/sync-procedures-status.md [+ skills/pace-sync/sync-procedures-entity.md] | | `setup` | skills/pace-sync/sync-procedures-setup.md | | `pull` | skills/pace-sync/sync-procedures-pull.md + skills/pace-sync/sync-procedures-entity.md(§1 ID 解析) |
Gate 结果同步(被动触发):skills/pace-sync/sync-procedures-push-advanced.md
Auto-link/create(Hook 触发):skills/pace-sync/sync-procedures-auto.md
输出
智能同步输出格式:
同步检测:
- 3 个实体有变更(CR-003 状态→developing, EPIC-001 完成度↑, PF-002 新增验收)
- 2 个新实体未关联(BR-003, CR-008)
- 7 个已关联且无变化
[用户确认后]
| 实体 | 类型 | 外部链接 | 操作 | 结果 |
|------|------|---------|------|------|
| EPIC-001 | Epic | [#10](URL) | 更新标签 | ✅ |
| BR-003 | BR | [#15](URL) | 新建 Issue | ✅ |
| CR-003 | CR | [#42](URL) | 更新标签 + Comment | ✅ |
汇总:3 已同步 / 2 新建 / 7 无变化
层级:2 个 sub-issue 关系已建立
Read more
description: Use when user says "同步/sync/同步到GitHub/关联Issue/unlink/Gate同步/sub-issue/全量同步/增量同步" or /pace-sync. Syncs Epic/BR/PF/CR to GitHub Issues. NOT for internal state (use /pace-dev). argument-hint: "[子命令] [参数]" allowed-tools: AskUserQuestion, Read, Write, Edit, Glob, Grep, Bash model: sonnet
/pace-sync — 外部工具同步
将 devpace 全部实体(Epic/BR/PF/CR)与外部项目管理工具同步。支持 GitHub(当前),设计为 Linear/Jira 可扩展。
与现有机制的关系
- /pace-dev 管理 CR 内部状态转换 → /pace-sync 将状态变化推送到外部
- /pace-change 管理变更操作 → /pace-sync 同步变更后状态到外部
- /pace-release 管理发布流程 → /pace-sync 同步发布状态到外部
- /pace-review Gate 2 结果 → /pace-sync Gate 结果自动推送(Comment + 标签)
- /pace-status 展示内部状态 → /pace-sync status 展示同步状态和外部链接
推荐使用流程
首次配置:`setup` → 日常同步:`/pace-sync`(智能同步)→ 查看状态:`status`
输入
`$ARGUMENTS` 解析为子命令 + 参数。
子命令
| 子命令 | 参数 | 说明 | |--------|------|------| | sync | [--dry-run] | **智能同步**(默认行为):自动检测变更,呈现摘要,确认后执行。无参数时等价。 | | link | 实体ID [#外部ID] | 关联实体与已有外部 Issue(支持 EPIC-xxx/BR-xxx/PF-xxx/CR-xxx;省略外部 ID 则智能匹配) | | unlink | 实体ID | 解除实体与外部的关联 | | status | [--all] | 查看同步状态(--all 显示全部实体类型,默认仅 CR) | | setup | [--auto] | 引导式同步配置(--auto 跳过交互确认) | | pull | 实体ID | 查询外部状态,提示用户是否更新 devpace(轻量检查) |
**无参数时默认执行智能同步(sync)。**
**实体 ID 格式**:`EPIC-001`、`BR-002`、`PF-003`、`CR-004`(前缀确定类型)。纯数字默认为 CR(向后兼容)。
流程
1. 读取 `.devpace/integrations/sync-mapping.md`(不存在 → 引导 `setup`) 2. 加载 `skills/pace-sync/sync-procedures-common.md`(始终加载) 3. **根据子命令,仅加载对应的 procedures 文件**(均位于 `skills/pace-sync/` 目录):
| 参数 | 加载文件 | |------|---------| | `sync` / (空) | skills/pace-sync/sync-procedures-entity.md(智能同步主流程) | | `sync --dry-run` | skills/pace-sync/sync-procedures-entity.md(dry-run 模式) | | `link` | skills/pace-sync/sync-procedures-link.md + skills/pace-sync/sync-procedures-entity.md(§1 ID 解析) | | `unlink` | skills/pace-sync/sync-procedures-status.md + skills/pace-sync/sync-procedures-entity.md(§1 ID 解析) | | `status` [--all] | skills/pace-sync/sync-procedures-status.md [+ skills/pace-sync/sync-procedures-entity.md] | | `setup` | skills/pace-sync/sync-procedures-setup.md | | `pull` | skills/pace-sync/sync-procedures-pull.md + skills/pace-sync/sync-procedures-entity.md(§1 ID 解析) |
Gate 结果同步(被动触发):skills/pace-sync/sync-procedures-push-advanced.md
Auto-link/create(Hook 触发):skills/pace-sync/sync-procedures-auto.md
输出
智能同步输出格式:
同步检测: - 3 个实体有变更(CR-003 状态→developing, EPIC-001 完成度↑, PF-002 新增验收) - 2 个新实体未关联(BR-003, CR-008) - 7 个已关联且无变化 [用户确认后] | 实体 | 类型 | 外部链接 | 操作 | 结果 | |------|------|---------|------|------| | EPIC-001 | Epic | [#10](URL) | 更新标签 | ✅ | | BR-003 | BR | [#15](URL) | 新建 Issue | ✅ | | CR-003 | CR | [#42](URL) | 更新标签 + Comment | ✅ | 汇总:3 已同步 / 2 新建 / 7 无变化 层级:2 个 sub-issue 关系已建立
Give your Claude Code projects a steady development pace — requirements change, rhythm stays. A development harness for Claude Code — rules, schemas, gates, and feedback loops that keep AI-assisted development traceable and measurable.
Repo: arch-team/devpace
Other skills on devpace.
- /pace-biz
Use when user says "业务机会/OPP", "专题/Epic", "分解需求/decompose", "精炼/refine", "战略对齐/align", "业务全景/view", "需求发现/brainstorm/discover", "导入/import", "技术债务/infer", "pace-biz", or wants to plan requirements. NOT for /pace-dev, -change, -plan, -init.
Open skill - /pace-change
Use when user says "不做了", "搁置", "停掉", "加一个", "加需求", "追加", "改需求", "需求变了", "范围变了", "优先级调", "延后", "提前", "砍掉", "先做这个", "排到前面", "恢复", "捡回来", "pace-change", or wants to add, pause, resume, reprioritize, modify, undo, batch change, or query change history. NOT for code implementation
Open skill - /pace-dev
Use when user says "开始做", "帮我改", "实现", "修复", "继续推进", "编码", "写代码", "开发", "重构", "做个", "coding", "implement", "fix", "refactor", "build", /pace-dev, or explicitly requests to start/continue/resume coding work. "帮我改" only when target is code/UI/config. NOT for requirement changes
Open skill - /pace-feedback
Use when user reports issues, shares feedback, or receives production alerts — "用户反馈", "线上问题", "生产问题", "告警", "改进建议", "新需求", "体验问题", "功能请求", "线上bug", "运维", "事件", "incident", "故障", "P0", "P1", "严重故障", "postmortem", "事后复盘". NOT for code implementation or development (use
Open skill - /pace-guard
Use when user wants to assess risks before development, check current risk status, analyze risk trends, or says "风险/预检/预分析/guard/risk/隐患/安全检查". Also auto-invoked during advance mode intent checkpoint for L/XL CRs. NOT for /pace-dev (implementation), NOT for /pace-review (quality
Open skill - /pace-help
Use when user says "帮助", "help", "怎么用", "使用说明", "用法", "有哪些命令", "能做什么", "命令列表", "怎么入门", "quickstart", "FAQ", "常见问题", "pace-help", or wants help with how to use devpace commands and features. NOT for concept deep dive or methodology (use /pace-theory). NOT for next-step
Open skill

