菜单
Use when the user says "update the design doc", "sync DESIGN.md", "sync ARC42STORIES.MD", "reflect code changes in the design", or invokes /update-design. Also invoked by git-commit when commits affect architecture. Routes to the appropriate design doc workflow based on project type.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when the user says "review the code", "check these changes", "review this", "look at staged changes", or invokes /code-review. Also invoked automatically by git-commit skills if no review has been done this session. Applies to Java/Quarkus, TypeScript, and Python projects.
Use when the user says "bump a version", "upgrade dependencies", "check for newer versions", "add a dependency", or "run audit" — for Java/Maven, TypeScript/npm, or Python/pip projects. Routes to the correct package manager based on project type declared in CLAUDE.md.
Use when user wants to create a commit NOW — says "commit this", "commit these changes", "create a commit". Routes to Java or custom project workflows when CLAUDE.md declares those types; falls back to generic commit for all others. Does NOT apply to discussions about past commits or questions about whether to commit.
Use when the commit history contains noise — fixup commits, revert chains, docs wording chores, tiny cleanups — that obscures meaningful history. Also triggered when the pre-push hook flags squash candidates, or invoked on demand via /git-squash on any commit range.
Use when ending a mid-work session (branch stays open) and wanting to preserve context for resumption, OR when a session is beginning and needing to resume from where things left off — says "create a handover", "end of session", "update the handover", "write a handover", "wrap", or "resume handover". NOT for branch closure (use work-end — it includes the full wrap). NOT for project narrative (use write-content, diary type).
Use when setting up GitHub issue tracking, planning implementation work (creating epics and child issues from a plan), when a user request spans multiple concerns that should be separate issues, or when staged changes span multiple issues and should be split. Also invoked automatically throughout the development lifecycle when Work Tracking is enabled in CLAUDE.md.
| name | update-design |
| description | Use when the user says "update the design doc", "sync DESIGN.md", "sync ARC42STORIES.MD", "reflect code changes in the design", or invokes /update-design. Also invoked by git-commit when commits affect architecture. Routes to the appropriate design doc workflow based on project type. |
Reads project type, then loads the language-specific design sync workflow. All types update a living design document to reflect current architecture — only the document format and detection logic differ.
python3 ~/.claude/skills/project-init/ctx.py
Read PROJECT_TYPE from the output. Also read HAS_ARC42STORIES for design doc routing.
Extract: java | ts | python | generic
| Project type | File to read |
|---|---|
java | ~/.claude/skills/update-design/java.md |
ts | ~/.claude/skills/update-design/typescript.md |
python | ~/.claude/skills/update-design/python.md |
generic | ~/.claude/skills/update-design/typescript.md (lightweight fallback) |
Read the file, then execute the workflow it describes.
Invoked by: [git-commit] alongside [update-claude-md]; [adr] suggests running this when an ADR documents a new component
Invokes: None (terminal skill in the chain)
Complements: adr — captures point-in-time decisions alongside this skill's living-doc updates