consolidate
Apply an approved sub-skill grouping by moving user-specified skills into a parent bundle, with timestamped backups of every modified directory.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 8.2k
- Forks
- 1.4k
01 前言 Front Matter
- name
- consolidate
- description
- Apply an approved sub-skill grouping by moving user-specified skills into a parent bundle, with timestamped backups of every modified directory.
- disable-model-invocation
- true
03 SKILL.md 正文
Consolidate sub-skills (sub-skill.consolidate)
Execute the reorganization by moving user-specified skills into a parent bundle, forming a sub-skill hierarchy.
When to use
- The user has approved a grouping proposal (typically from
sub-skill.review) and wants to apply it. - Migrating standalone skills into a new or existing parent bundle.
Process
- Confirm the plan. Restate which skills will move and where, and ask the user to confirm before making any file changes.
- Back up every original skill directory. Before moving anything, create a timestamped backup of each skill directory that will be modified.
- For a skill at
<root>/<skill-name>/SKILL.md, back up the entire<skill-name>directory:cp -r <skill-name> "<skill-name>.$(date +%Y%m%d-%H%M%S).bak" - Keep all backups; never overwrite an existing backup file.
- For a skill at
- Create or update the parent bundle.
- If the parent does not exist, create
<parent-name>/SKILL.mdwithhas-sub-skill: truein the frontmatter. - If the parent already exists, ensure its frontmatter includes
has-sub-skill: true.
- If the parent does not exist, create
- Move child skills into the parent. Move each child skill's entire directory under the parent bundle.
- Example:
web-search/→web-research/web-search/
- Example:
- Keep documentation directory alignment. When moving documentation, references, examples, assets, or other payload directories, align them with the new skill directory layout.
- Preserve relative links from
SKILL.mdto files such asreferences/,assets/,examples/, or templates. - If a child skill moves from
<root>/<child>/to<root>/<parent>/<child>/, its documentation payload should move with that child unless the approved plan says otherwise. - Do not leave documentation in the old location or merge unrelated documentation directories together.
- Preserve relative links from
- Verify the result. List the new directory structure and confirm each moved skill still has a valid
SKILL.mdwith required frontmatter (nameanddescription). Check documentation directory alignment and relative links after the move. - Report the change. Summarize what was moved, the new structure, any documentation directories that moved, and where backups are located.
Don'ts
- Never move skills without backing up first.
- Never overwrite an existing backup — always use a fresh timestamped suffix.
- Don't drop frontmatter or payload files during the move; the entire directory must be preserved.
- Don't break documentation directory alignment — references, assets, examples, and templates must stay aligned with the skill directory that uses them.
- Don't create deeply nested hierarchies (3+ levels) unless the user explicitly requests it.
04 同仓库更多 Skills
golden-skill
Golden fixture skill
tools
暂无简介
review
Analyze the available skill set and recommend candidate groups that could be consolidated into sub-skill bundles. Read-only — proposes a plan, does not move files.
sub-skill
Discover and reorganize the skill inventory into hierarchical sub-skill bundles. Use when the user asks to review, group, or consolidate skills into a parent bundle.
write-tui
Use when writing or modifying the kimi-code terminal UI in apps/kimi-code/src/tui — components, dialogs/selectors, slash commands, themes, streaming render, or the KimiTUI controllers. Covers the architecture, where new features go, test placement, the theme system mechanics, and the dialog interaction/visual spec (DESIGN.md).
write-pr
在 kimi-code 仓库里创建或更新 PR 时使用:如何写出让 reviewer 只读描述就能从逻辑和架构上理解改动的 PR 描述,包括核心思路与结构图、"行为变化与受影响人群"表、可视化大纲,以及 UI/UX 变化的截图和录屏。