菜单
Tick off completed acceptance-criteria checkboxes in a linked issue/ticket or PR body after finishing and pushing the corresponding work. Use right after pushing commits to a PR, before reporting the task as done.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Address code review comments (e.g. from Copilot's automated PR review) on an open PR, then mark each resolved conversation. Use after a reviewer leaves inline comments and you've fixed and pushed the corresponding changes.
Write or update a GitHub PR description for this repo. Use when the user asks to create, update, or improve a pull request's description/body.
Prepare a versioned release notes document for the Firely CQL SDK. Use when the user asks to write, draft, or cut release notes for a new version.
Create or edit a GitHub issue for this repo. Use when the user asks to file a bug, write up an issue, or edit an existing issue's body.
Regenerate ELM JSON files after adding or changing CQL input files in a test/library-set project (e.g. CoreTests/Input/ELM/HL7). Use when the user adds CQL files and needs the corresponding ELM generated.
Pick up a GitHub issue/ticket by number or URL — find or create its branch and check it out. Use when the user says to pick up, start, or work on a specific ticket/issue number.
| name | sync-acceptance-criteria |
| description | Tick off completed acceptance-criteria checkboxes in a linked issue/ticket or PR body after finishing and pushing the corresponding work. Use right after pushing commits to a PR, before reporting the task as done. |
After pushing work to a PR, check whether the linked issue and/or the PR body has an "Acceptance Criteria" (or similar) checklist, and update it to reflect what's actually true on the pushed branch:
gh issue view <n> --json body -q '.body' / gh pr view <n> --json body -q '.body') — never edit from a stale copy, since someone (or an earlier step in the same session) may have changed it since you last read it.grep for the thing) before checking it off. Never check off a criterion you haven't actually verified — a false positive here is worse than leaving it unchecked for a human to confirm.- [ ] → - [x] for verified-complete items; leave everything else (including unmet or partially-met criteria) untouched.gh issue edit --body-file / gh pr edit --body-file on a temp file (never --body inline). If gh pr edit/gh issue edit fails on an unrelated error, fall back to the REST PATCH: gh api repos/<owner>/<repo>/issues|pulls/<number> -X PATCH --input <json-file> with a {"body": "..."} payload.write-pr-description skill's note on gh pr edit failing on an unrelated GraphQL error).