CommandCodeAI / CommandCodeAI/command-code
feat: `cmd skills update` -- record install source so skills can be updated
还没有人认领这个 Issue。
- 主要语言
- 没有语言数据
- 星标
- 4k
- 派生
- 350
- PR 合并指标
- 30 天内没有已合并 PR
描述
Problem
cmd skills add does not record where a skill came from. Once installed, there is no manifest mapping skill name to source repo -- nothing in ~/.commandcode/ or the skill directory preserves the owner/repo[/path][@ref] spec used at install time.
Consequence: there is no way to update an installed skill from within the CLI. cmd skills only has add / remove / list (unchanged since v0.18.2). The only update path is:
- Rediscover the source repo yourself (out of band -- the CLI can't tell you)
- Re-run
cmd skills add <owner/repo/path> -f
For skills installed from multi-skill repos or subpaths (e.g. cmd skills add acme/repo/path/to/skill), rediscovering the exact spec is genuinely error-prone.
Prior art
- Mods already solve this in Command Code itself:
cmd mods updatereinstalls and reconciles every configured mod package, because mod sources are tracked insettings.json. Skills are the odd one out. - GitHub CLI shipped
gh skill(v2.90.0, April 2026), which records provenance metadata at install time and supportsgh skill update [name|--all]across agent hosts.
Proposal
- At
cmd skills addtime, write the resolved source spec (owner/repo[/path][@ref]plus installed commit SHA) to a manifest -- either askills.jsonalongside the skills directory or a per-skill metadata file. - Add
cmd skills update [skill-name]andcmd skills update --all: re-fetch from the recorded source and overwrite in place (same semantics asadd -f). cmd skills listcould then also show source + whether upstream has moved.
Part 1 is the load-bearing piece -- without provenance, no update verb is possible. Backfill for already-installed skills can be manual (prompt on first update, or accept a spec argument to re-pin).
Tested on v1.5.0 (macOS); docs at commandcode.ai/docs/skills confirm only add/list/remove exist.
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从现有的 cmd skills add、list 和 remove 入口开始,然后比较 cmd mods update 使用的 settings.json 中的来源处理方式。完成的标准是安装能够保留源规范和 commit SHA,同时 cmd skills update [skill-name] 和 --all 可以重新获取并覆盖已安装的 skills;检查 skills 文档以了解当前的命令界面。
由索引模型根据 Issue 内容生成。
评估
- 领域
- cli
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 48/100