一键导入
fix-issue
Analyze and fix a GitHub issue end-to-end, producing a PR
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Analyze and fix a GitHub issue end-to-end, producing a PR
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Pull user bug reports from the bindery Discord and convert them to GitHub issues
Sweep open issues and PRs, categorize, and propose a work queue
Use when picking a branch name, staging files, or writing a commit message — covers branch conventions, the project's Conventional Commits format with the scope vocabulary observed in history, and the documentation-update gate that fires before every commit (`docs/*`, `README.md`, godoc, Helm values).
Use when opening or updating a pull request, responding to review, or filing a GitHub issue — covers the PR body skeleton matched to recent merged PRs, draft → ready → squash mechanics, rebase-vs-merge policy, and the issue-template routing (`bug_report.yml` / `feature_request.yml`, blank issues disabled).
Use when deciding whether to run an out-of-process test suite (real binary or live instance) — picks between `make smoke`, `make abs-contract`, and `make predeploy-smoke` after the unit suite passes but you've changed handler wiring, scheduler jobs, downloader integration, ABS imports, or anything that boots the binary. For the routine pre-PR matrix (lint / vet / test / typecheck / build) see the `testing` skill.
Use when cutting a release — composing the `## [vX.Y.Z]` `CHANGELOG.md` section, picking the version bump, and walking commits since the last tag. Authoring only; the maintainer pushes the tag (which triggers GoReleaser + provenance signing) and the deploy bot auto-bumps Helm `values.yaml`.
| name | fix-issue |
| description | Analyze and fix a GitHub issue end-to-end, producing a PR |
| disable-model-invocation | true |
Fix GitHub issue $ARGUMENTS.
gh issue view <n> — read the issue and all comments. If reproduction steps are missing, say so and draft a comment asking for them (tone rules in CLAUDE.local.md) instead of guessing.fix/<n>-<slug>. Address the root cause, not the symptom.main with Fixes #<n>, summarize the root cause in the body.Never tag a release from this workflow — releases follow the flow in CLAUDE.md and are Vincent's call.