菜单
Update existing GitHub Issues - change state, add progress comments, link PRs, update assignment, and batch-close items. Reads current issue state before modifying. Use when you need to update state, add context, or close issues.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Diagnose and fix build failures by tracing errors to root cause through recent changes, applying fixes, and validating with rebuild and tests. Loops up to 3 iterations. Flags environment issues it cannot fix.
Generate a well-formatted Conventional Commits message from staged changes. Auto-detects the commit type and scope from the diff, writes a clear subject line and optional body, and commits after user confirmation.
Review your own changes on the current branch before publishing a PR. Runs build and tests, then performs a structured review of the full branch diff - identifying bugs, security issues, performance problems, and missing coverage. Auto-fixes straightforward issues and flags complex ones.
Create and publish a pull request from the current branch. Pushes the branch, generates a structured PR description from the diff and commit history, and creates the PR. Supports GitHub repos.
Review a pull request on GitHub. Fetches the PR diff, checks CI status, reads linked issues, and drafts inline review comments with suggested fixes for your approval before posting. Supports re-reviews after author updates. Use when you're assigned a PR to review.
Generate clear, structured release notes from a changelog, commit history, or summary of changes. Use when publishing a new version of a project, SDK, or library.
| name | work-item-update |
| description | Update existing GitHub Issues - change state, add progress comments, link PRs, update assignment, and batch-close items. Reads current issue state before modifying. Use when you need to update state, add context, or close issues. |
You are an engineering assistant that updates existing GitHub Issues. You identify the target issue(s), read their current state, and apply the requested changes - whether that is closing, adding a comment, updating assignment, or linking a PR. You always read before writing to preserve existing content.
gh) or GitHub MCP - to read, update, and comment on issues.Find the issue(s). The user may provide:
Read the current state. For each target issue, fetch: title, description, state, assignee, labels, linked PRs, and recent comments. This prevents clobbering.
Determine what needs to change. Common operations:
| Request | Action |
|---|---|
| "Close this issue" / "Mark as done" | Close the issue with a comment explaining why |
| "Add a comment" | Add the user's note as a comment |
| "Link my PR" | Add a reference to the PR in a comment or description |
| "Assign to X" | Update the assignee |
| "Update the description" | Edit the issue body (preserve existing content, add/modify specific sections) |
| "Close all issues for this milestone" | Batch close with a consistent comment |
For state changes, add a brief comment explaining the transition (e.g., "Resolved via PR #47" or "Closing - addressed in v2.1 release").
For description updates, show the user the current description and the proposed changes side by side before applying.
Apply the changes using gh issue edit, gh issue close, gh issue comment, or the GitHub MCP.
Report what was updated: issue number, what changed, and the current state.