菜单
Update the project's CLAUDE.md with meta learnings, conventions, gotchas, and significant codebase changes. Use when the user asks to update CLAUDE.md, capture learnings, document project conventions, or reflect recent work in the project guide.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Manage git worktrees using the gwm script. Supports creating, listing, removing, and checking status of worktrees. Use when the user says "create git worktree", "new worktree", or needs to work with multiple branches simultaneously via git worktrees.
Review the current Pull Request that has been checked out locally with structured feedback on code quality, issues, testing, and suggestions. Use when you need a comprehensive code review of a PR branch.
Catch up on branch changes by reviewing all changes between current branch and master/main, analyzing key files, and providing a comprehensive summary. Use when you need to understand what changed in a feature branch.
Perform a refactor pass focused on simplicity after recent changes. Use when the user asks for a refactor/cleanup pass, simplification, or dead-code removal and expects build to verify behavior.
Analyze the specified function from the given file with detailed line-by-line breakdown. Use when you need to understand what a function does, how it works, and why it was implemented that way.
Display Claude conversation history in an easy-to-scan format showing recent sessions with dates, projects, and topics. Use when you want to review past conversations or resume a previous session.
| name | update-claude-md |
| description | Update the project's CLAUDE.md with meta learnings, conventions, gotchas, and significant codebase changes. Use when the user asks to update CLAUDE.md, capture learnings, document project conventions, or reflect recent work in the project guide. |
| disable-model-invocation | true |
CLAUDE.md is the project's institutional knowledge — the things a new developer (or a new Claude session) needs to know that aren't obvious from the code itself. The goal is to keep it concise, current, and high-signal.
Include information that saves future sessions from re-discovering things the hard way:
Skip anything that's either ephemeral or derivable from the code:
Rule of thumb: Would you tell a new developer this on their first day? If yes, add it. If it's just details about today's work, skip it.
git log --oneline -20 and git diff HEAD~5..HEAD --stat to identify significant changes. Look for patterns: new scripts, moved directories, changed conventions, recurring issues.After updating, summarize: