Use when Comet change 验证已通过,需要用户确认归档、合并 delta spec,或恢复 archive 阶段。
Source text: Chinese
Menu
Skills in this repository
SkillsMP has collected 5,252 skills from TuYv/ccpm. Open a skill to review its source and details.
TuYv/ccpmShowing 40 of 5,252 collected skills.
Use when Comet change 验证已通过,需要用户确认归档、合并 delta spec,或恢复 archive 阶段。
Source text: Chinese
在保留已确认语义、仓库结构、子模块边界和聚焦验证的前提下,同步 Comet 中英文文档、README、Skill、发布说明和网站页面。文档变更需要保持双语,或中文措辞需要英文对应版本时使用。
Source text: Chinese
Use when full Comet change 已完成 design 阶段,需要创建/恢复实施计划、选择执行方式或继续 build 阶段任务。
Source text: Chinese
Comet Phase 5: Archive. Invoke with /comet-archive. Merge delta specs into main specs with OpenSpec semantics, archive change.
Comet Phase 3: Plan and Build. Invoke with /comet-build. Create plans and select execution method (subagent or direct) for implementation.
Comet Phase 2: Deep Design. Invoke with /comet-design. Produce Design Doc and delta spec through brainstorming.
Comet preset path: Bug fix / hotfix. Skip brainstorming, directly open → build → verify → archive. Applicable for behavior fixes, scenarios not involving new capability design.
Comet Phase 1: Open. Invoke with /comet-open. Explore ideas through OpenSpec, confirm requirements clarification, then create change structure (proposal + design + tasks).
Comet — OpenSpec + Superpowers dual-star development workflow. Start with /comet for automatic phase detection and dispatch to subcommands. Five phases: open → design → build → verify → archive.
Comet preset path: Non-bug small changes (tweak). Skip brainstorming and full plan, directly open → lightweight build → light verify → archive. Applicable for copy, configuration, documentation or prompt local optimization.
Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.
Comet Classic workflow (OpenSpec + Superpowers). Use when the user invokes /comet-classic, asks to start or resume it, or resume-probe returns an unambiguous active Classic change.
Use when full Comet change 已完成 open 阶段但缺少 Superpowers Design Doc,或 design 阶段需要从 OpenSpec 交接包恢复。
Source text: Chinese
使用 PR 当前准确 head、失败 job 日志、本地复现边界和可合并状态,诊断 Comet PR 的 GitHub Actions 与覆盖率检查。PR 出现 CI 报错、Codecov 问题、过期检查或无法解释的红色 job 时使用。
Source text: Chinese
基于当前代码库,将本地 Comet 想法、观察到的回归或改进提案整理为聚焦的 GitHub Issue 草稿。用户要求把本地调查转换为 Issue、后续 Issue、Bug、Feature 或维护任务时使用。
Source text: Chinese
在隔离范围内,通过所属 Native 或 Classic workflow、匹配风险的测试、生成 Runtime 检查和谨慎交付,实施已确认的 Comet GitHub Issue 或 review 阻塞项。用户明确要求修复已验证的 Issue 或 PR 问题时使用。
Source text: Chinese
对照当前仓库契约、源码、Runtime、测试和安装行为,验证并分类 Comet GitHub Issue。用户询问 Issue 是否真实、可复现、重复、已实现、属于配置问题,或是否适合后续处理时使用。
Source text: Chinese
以只读、证据优先的方式审阅 Comet 社区 PR,包括最新 diff、关联 Issue、review thread 状态、可合并性和 CI。用户要求审阅 PR、判断评论是否仍然有效,或准备简洁的合并阻塞评论时使用。
Source text: Chinese
将 Comet GitHub 维护请求路由到基于证据的 PR 审阅、Issue 分诊、本地想法收集、CI 诊断或 Issue 实施流程。用户提到 Comet GitHub Issue/PR 但未指定流程,或询问下一步如何处理时使用。
Source text: Chinese
Use when 用户要修复已有行为 bug,且不新增 capability、不需要完整设计;也用于恢复 hotfix workflow。
Source text: Chinese
Comet Native workflow. Use when the user explicitly invokes /comet-native, asks to start or resume a Native change, or the entry router selects Native.
Use when Comet 需要创建新的 OpenSpec change,或 active change 缺少 proposal/design/tasks/.comet.yaml 初始化产物。
Source text: Chinese
根据真实版本和分支范围准备 Comet 发布或发布说明更新,保持 Changelog 面向用户、双语网站文档一致、生成资产已验证,并明确 Git 交付边界。Beta、hotfix、版本检查、发布说明或发布就绪检查时使用。
Source text: Chinese
通过区分过期配置与源码缺陷,并执行真实打包 Runtime 路径,诊断 Comet Hook、安装、路由、平台、生成 Runtime 或生命周期行为。Hook 或安装报告可能涉及配置、生成资产漂移、不支持的平台或跨项目归属问题时使用。
Source text: Chinese
在保护无关脏改动、关联 worktree、子模块和用户明确边界的前提下,提交、推送、合并或完成范围明确的 Comet 变更。用户要求提交、推送、合并回目标分支、清理 worktree 或交付已准备好的改动时使用。
Source text: Chinese
Use when 用户要启动或恢复 Comet 工作流,需要根据 active change、.comet.yaml、hotfix/tweak 意图路由到对应阶段 Skill。
Source text: Chinese
Use when 用户要进行可收敛为单一 OpenSpec change 的轻量或中等变更,且不需要完整设计;也用于恢复 tweak workflow。
Source text: Chinese
Use when Comet change 已完成 build 阶段,需要验证实现、处理验证失败决策或完成分支收尾。
Source text: Chinese
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Archive multiple completed changes at once. Use when archiving several parallel changes.
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.