菜单
Update project documentation based on recent changes and current codebase state. Use when the user says 'update docs', 'update readme', 'sync docs', 'docs are stale', 'update CLAUDE.md', 'refresh documentation', or any variation of wanting documentation updated.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when working with Jira or Confluence from command line, including authentication, searching issues with JQL, bulk operations, sprint reports, or creating/updating work items using acli
Pick and work on the next incomplete item from TODO.md. Use when the user says 'what's next', 'next task', 'next todo', 'what should I work on', 'what's up next', 'pick a task', 'grab something from the TODO', 'what tasks remain', 'work on the next task', 'what can I tackle next', or any variation of wanting to pick and work on the next incomplete TODO item.
Create or append tasks to TODO.md in the current working directory. Use when the user says 'add todo', 'add a task', 'TODO:', 'new task', 'track this', 'note this down', 'add to the backlog', 'before I forget', or any variation of wanting to capture new items. Also applies when the user finishes work and mentions follow-up items to save for later. Not appropriate for reading, viewing, checking off, removing, or reorganizing TODO.md.
Commit pending changes to git, optionally pushing after. Use when the user says 'commit', 'commit my changes', 'commit all', 'commit everything', 'save my work to git', 'stage and commit', or any variation of wanting to create a git commit. Accepts an optional 'push' keyword to push after committing, and optionally specific file names or a description of what to commit.
Review a pull request for issues and feedback. Use when the user says 'review this PR', 'check this PR', 'look at PR changes', 'review the diff', 'what do you think of this PR', 'post review comments', 'any issues with this PR', 'what changed in this PR', 'are there problems with these changes', 'critique the diff', or any variation of wanting PR feedback or code review.
Run one or more release actions: version, changelog, docs, commit, tag, push, watch, release. With no arguments, auto-detects needed actions from repo state and asks for confirmation. Use when the user says 'ship', 'ship it', 'ship <target>', 'version and push', 'tag and push', 'bump version and push', 'release', 'cut a release', 'publish', 'ship and watch', 'push and watch CI', 'tag and watch', or any combination of these release steps.
| name | update-docs |
| description | Update project documentation based on recent changes and current codebase state. Use when the user says 'update docs', 'update readme', 'sync docs', 'docs are stale', 'update CLAUDE.md', 'refresh documentation', or any variation of wanting documentation updated. |
Verify and update project documentation so it accurately reflects the current state of the codebase. Do not commit or push the changes to git unless also asked to do so. Do not include volatile metrics (test counts, coverage percentages, line counts) that become stale quickly.
Glob for **/*.md to find all doc files. Read each one.
For each doc file, spot-check its claims against the codebase using Glob and Grep — focus on things likely to have changed (skill lists, plugin names, file paths, commands). Skip claims that are obviously stable.
Edit files directly. Do not produce a report first.
Treat CLAUDE.md and README.md in the same directory as a pair — they cover the same component from different angles. Update both when updating one.
./CLAUDE.md, ./.claude/CLAUDE.md, ./AGENTS.md and any nested CLAUDE.md files in subdirectoriesls), obvious language conventions, and anything the agent can trivially discover