Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
端到端的 GitHub issue 修复工作流。接受 issue 编号作为参数，从查看 issue 到建分支、实现修复、推送、开 PR、处理评审、合并的完整流程。当用户请求"修复 issue
Install Fix Issue
$ npx skills add sky1wu/Bili-SyncPlay --skill fix-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sky1wu/Bili-SyncPlay fix-issue --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sky1wu/Bili-SyncPlay.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/fix-issue .claude/skills/fix-issue && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "fix-issue" agent skill from https://github.com/sky1wu/Bili-SyncPlay/tree/main/.claude/skills/fix-issue into .claude/skills/fix-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-issue", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sky1wu/Bili-SyncPlay/tree/main/.claude/skills/fix-issueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sky1wu/Bili-SyncPlay --skill fix-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sky1wu/Bili-SyncPlay fix-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sky1wu/Bili-SyncPlay.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/fix-issue .agents/skills/fix-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fix-issue" agent skill from https://github.com/sky1wu/Bili-SyncPlay/tree/main/.claude/skills/fix-issue into .agents/skills/fix-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-issue", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sky1wu/Bili-SyncPlay --skill fix-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sky1wu/Bili-SyncPlay fix-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sky1wu/Bili-SyncPlay.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/fix-issue .cursor/skills/fix-issue && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "fix-issue" agent skill from https://github.com/sky1wu/Bili-SyncPlay/tree/main/.claude/skills/fix-issue into .cursor/skills/fix-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-issue", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sky1wu/Bili-SyncPlay.git --path .claude/skills/fix-issue--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sky1wu/Bili-SyncPlay --skill fix-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sky1wu/Bili-SyncPlay fix-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sky1wu/Bili-SyncPlay.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/fix-issue .gemini/skills/fix-issue && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "fix-issue" agent skill from https://github.com/sky1wu/Bili-SyncPlay/tree/main/.claude/skills/fix-issue into .gemini/skills/fix-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-issue", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sky1wu/Bili-SyncPlay fix-issueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sky1wu/Bili-SyncPlay --skill fix-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sky1wu/Bili-SyncPlay.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/fix-issue .github/skills/fix-issue && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "fix-issue" agent skill from https://github.com/sky1wu/Bili-SyncPlay/tree/main/.claude/skills/fix-issue into .github/skills/fix-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-issue", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sky1wu/Bili-SyncPlay --skill fix-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sky1wu/Bili-SyncPlay fix-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sky1wu/Bili-SyncPlay.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/fix-issue .opencode/skills/fix-issue && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "fix-issue" agent skill from https://github.com/sky1wu/Bili-SyncPlay/tree/main/.claude/skills/fix-issue into .opencode/skills/fix-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fix-issue", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
fix-issue- GitHub stars
- 168
- Token cost
- ~590 tokens
- SKILL.md length
- 152 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
端到端的 GitHub issue 修复工作流。接受 issue 编号作为参数，从查看 issue 到建分支、实现修复、推送、开 PR、处理评审、合并的完整流程。当用户请求"修复 issue
- Works in 8 steps: 校验 $1 为纯数字 → 了解 issue → 创建 feature 分支（严禁在 main 上工作） → …
- Development work in your project
- SKILL.md covers 0. 校验 $1 为纯数字, 1. 了解 issue, 2. 创建 feature 分支（严禁在 main 上工作） and 3. 实现修复 + 测试, plus 5 more sections
- Calls git, npm and gh
What it does
Fix Issue is an agent skill from sky1wu/Bili-SyncPlay. 端到端的 GitHub issue 修复工作流。接受 issue 编号作为参数，从查看 issue 到建分支、实现修复、推送、开 PR、处理评审、合并的完整流程。当用户请求"修复 issue
Its SKILL.md is about 590 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with GitHub and Git. The repository describes itself as: Synchronize Bilibili playback across a room. The licence is GPL-3.0.
When your agent uses it
- Development work in your project
Example prompts
- “/fix-issue”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e0c87de. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitnpmgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, npm and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Fix Issue loads about 590 tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 152 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from sky1wu/Bili-SyncPlay at commit e0c87de, republished under its GPL-3.0 licence (© sky1wu). 152 words, ~590 tokens.
Download SKILL.mdSave it as
.claude/skills/fix-issue/SKILL.md (or your agent's skills folder).- name
- fix-issue
- description
- 端到端的 GitHub issue 修复工作流。接受 issue 编号作为参数，从查看 issue 到建分支、实现修复、推送、开 PR、处理评审、合并的完整流程。当用户请求"修复 issue
fix-issue — 端到端 GitHub Issue 修复流程
以 $1 作为 issue 编号，严格按以下顺序执行。任何一步失败都先修复再进下一步，不要跳步。
0. 校验 $1 为纯数字
$1 必须匹配 ^[0-9]+$。若不是，停止执行并提示用户改用 add-feature 或先给出 issue 编号。
ISSUE_NUM="$1" # 后续命令一律使用此变量，不要直接拼 $11. 了解 issue
gh issue view "$ISSUE_NUM"- 通读正文、评论、关联 PR、标签。
- 明确问题边界：是 bug、feature 还是重构？涉及哪些模块？
- 如果描述不清，先向用户确认范围再动手。
2. 创建 feature 分支（严禁在 main 上工作）
git switch main && git pull --ff-only
git switch -c "fix/issue-$ISSUE_NUM"- 开工前确认当前分支。如在
main/master，立即切到 feature 分支再开始改动。 - 分支命名：
fix/issue-$ISSUE_NUM；若 issue 其实是新功能需求，改用add-feature技能。 - 创建后
git rev-parse --abbrev-ref HEAD再确认一次。
3. 实现修复 + 测试
- 先读相关代码路径，枚举所有受影响的调用点和姊妹路径（状态清理、错误处理、异步 await 等）。
- 状态类 bug：grep 所有相关字段和每个 reset/cleanup 点，逐一确认。
- 校验类 bug：列出每个入口点。
- 异步 Redis/锁操作：务必
await并包裹try/catch。 - 新增或修改单元测试覆盖修复面。
4. 提交前的预提交检查（强制）
npm run format:check && npm run lint && npm run typecheck && npm run build && npm test && npm run audit任一项失败就先修复，不要跳过。CLAUDE.md 的 Git 工作流已明确要求这一步。
npm run audit 不被 npm test 覆盖，是 CI verify job 的同一道依赖闸门，且会在
本地毫无改动的情况下因新公告而变红——所以要在推送前跑，而不是等 CI 红了再补。不
适用于本仓库的条目写进 audit-allowlist.json，附理由和必填的过期日期。
5. 提交、推送、开 PR
git add <具体文件>
git commit -m "fix: <简明的'为什么'，而不是'做了什么'> (#$ISSUE_NUM)"
git push -u origin "fix/issue-$ISSUE_NUM"
PR_BODY=$(printf '## Summary\n- 变更点 1\n- 变更点 2\n\nFixes #%s\n\n## Test plan\n- [ ] 单元测试\n- [ ] 手动验证（如适用）\n' "$ISSUE_NUM")
gh pr create --title "fix: ..." --body "$PR_BODY"- 使用 Conventional Commits：
fix:、feat:、refactor:等。 - 一个可评审单元一次提交。
- 严禁
git add -A/git add .，避免误带入敏感文件或临时产物。
6. 等 Codex 评审，处理所有相关路径
- 收到评审反馈后：不要只修被标的那一行，对整类 bug 审视所有相关代码路径。
- 自审一轮：
grep代码库里与被标关注点相关的调用点和姊妹函数，逐一列出确认。 - 处理完再次跑第 4 步的完整预提交序列。
- 修复后再推一次，等下一轮评审直至通过。
7. 合并并清理
gh pr merge --squash --delete-branch
git switch main && git pull --ff-only- 只有在 CI 绿且评审通过后才合并。
- 合并后本地分支一并清理。
硬性规则
- 严禁直接推 main/master。
- 严禁跳过
format:check/lint/typecheck/build/test/audit。 - 严禁
--no-verify或--no-gpg-sign绕过钩子。 - 严禁
git add -A/git add .。 - 除非用户明确授权，否则
gh pr merge前先向用户确认。
© sky1wu, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/fix-issue of sky1wu/Bili-SyncPlay.
Open the folder on GitHubat commit e0c87de
Compare with similar skills
Fix Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Fix Issue this skillsky1wu/Bili-SyncPlay | 168 | — | ~590 | Automated safety check: Pass | GPL-3.0 | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Create Pull Requestcline/cline | 70k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Pull Request Title and Body Writeropeninterpreter/openinterpreter | 69k | 2 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Draft Release Notesjamiepine/voicebox | 57k | — | ~941 | Automated safety check: Pass | MIT | |
| PR Review State Fetchprisma/orm | 48k | — | ~767 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
Pull Request Title and Body Writer
openinterpreter/openinterpreter
Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.
Draft Release Notes
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
- Official
PR Review State Fetch
prisma/orm
Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
More from sky1wu/Bili-SyncPlay
Review Round
sky1wu/Bili-SyncPlay
处理当前 PR 的一轮 Codex 评审反馈。从读取评审信号、逐条定位根因、修复、验证、回复线程到推送的完整单轮流程。当用户请求"处理评审意见"、"处理下一轮反馈"、"看看 Codex 说了什么"或类似单轮评审响应任务时触发。不负责合并。
Add Feature
sky1wu/Bili-SyncPlay
端到端的 GitHub feature 开发工作流。接受 feature 简述或 issue 编号，从澄清需求到建分支、设计、实现、测试、推送、开 PR、处理评审、合并的完整流程。当用户请求"新增功能 X"、"实现 feature Y"、"给我加一个 ..."等端到端特性开发任务时触发。
Related
Categories
Questions about Fix Issue
What does Fix Issue do?
端到端的 GitHub issue 修复工作流。接受 issue 编号作为参数，从查看 issue 到建分支、实现修复、推送、开 PR、处理评审、合并的完整流程。当用户请求"修复 issue. Fix Issue is an agent skill from sky1wu/Bili-SyncPlay.
When should I use Fix Issue?
Fix Issue fits situations like: development work in your project.
How do I install Fix Issue in Claude Code?
Run `npx skills add sky1wu/Bili-SyncPlay --skill fix-issue -a claude-code`. Or copy the skill folder (.claude/skills/fix-issue in sky1wu/Bili-SyncPlay) into .claude/skills/fix-issue in your project. Claude Code loads it when a task matches its description.
How do I install Fix Issue in Codex?
Run `npx skills add sky1wu/Bili-SyncPlay --skill fix-issue -a codex`. Or copy the skill folder (.claude/skills/fix-issue in sky1wu/Bili-SyncPlay) into .agents/skills/fix-issue in your project. Codex loads it when a task matches its description.
Can I use Fix Issue in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sky1wu/Bili-SyncPlay --skill fix-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fix-issue, .gemini/skills/fix-issue, .github/skills/fix-issue and .opencode/skills/fix-issue in your project.
What does Fix Issue need to run?
Going by SKILL.md and its folder, Fix Issue needs the command-line tools its instructions call (git, npm and gh).
Does Fix Issue access the network?
SKILL.md contains no URLs. Its commands use git, npm and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Fix Issue safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Fix Issue use?
Fix Issue is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Fix Issue use?
About 590 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Fix Issue?
Skills that share tags, products or a category with Fix Issue: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Pull Request Title and Body Writer (openinterpreter/openinterpreter, 69k stars) and Draft Release Notes (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fix Issue?
sky1wu (a GitHub user) maintains it in sky1wu/Bili-SyncPlay, which has 168 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 21, 2026.
Source: sky1wu/Bili-SyncPlay on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.