Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Turn a known bug into a tight, red-capable reproducer, then prove the reproducer locks that bug with a reversal negative control (reintroduce the bug → reproducer must go red again).
Install Bug Reproduce
$ npx skills add Prismer-AI/PrismerCloud --skill bug-reproduce -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Prismer-AI/PrismerCloud bug-reproduce --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/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sdk/apc/skills/bug-reproduce .claude/skills/bug-reproduce && 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 "bug-reproduce" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/bug-reproduce into .claude/skills/bug-reproduce/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-reproduce", 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/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/bug-reproduceType 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 Prismer-AI/PrismerCloud --skill bug-reproduce -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Prismer-AI/PrismerCloud bug-reproduce --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .agents/skills && cp -r skills-src/sdk/apc/skills/bug-reproduce .agents/skills/bug-reproduce && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "bug-reproduce" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/bug-reproduce into .agents/skills/bug-reproduce/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-reproduce", 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 Prismer-AI/PrismerCloud --skill bug-reproduce -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Prismer-AI/PrismerCloud bug-reproduce --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/sdk/apc/skills/bug-reproduce .cursor/skills/bug-reproduce && 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 "bug-reproduce" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/bug-reproduce into .cursor/skills/bug-reproduce/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-reproduce", 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/Prismer-AI/PrismerCloud.git --path sdk/apc/skills/bug-reproduce--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 Prismer-AI/PrismerCloud --skill bug-reproduce -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Prismer-AI/PrismerCloud bug-reproduce --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/sdk/apc/skills/bug-reproduce .gemini/skills/bug-reproduce && 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 "bug-reproduce" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/bug-reproduce into .gemini/skills/bug-reproduce/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-reproduce", 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 Prismer-AI/PrismerCloud bug-reproduceInstalls 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 Prismer-AI/PrismerCloud --skill bug-reproduce -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .github/skills && cp -r skills-src/sdk/apc/skills/bug-reproduce .github/skills/bug-reproduce && 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 "bug-reproduce" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/bug-reproduce into .github/skills/bug-reproduce/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-reproduce", 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 Prismer-AI/PrismerCloud --skill bug-reproduce -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Prismer-AI/PrismerCloud bug-reproduce --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Prismer-AI/PrismerCloud.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/sdk/apc/skills/bug-reproduce .opencode/skills/bug-reproduce && 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 "bug-reproduce" agent skill from https://github.com/Prismer-AI/PrismerCloud/tree/main/sdk/apc/skills/bug-reproduce into .opencode/skills/bug-reproduce/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bug-reproduce", 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
bug-reproduce- GitHub stars
- 1.6k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 420 words
- Files
- 2
- Skills in repo
- 88
- Repo updated
- First seen
- Licence
- MIT
At a glance
Turn a known bug into a tight, red-capable reproducer, then prove the reproducer locks that bug with a reversal negative control (reintroduce the bug → reproducer must go red again).
- Works in 5 steps: 钉环境 + 建复现器（RED） → 最小 fix（GREEN） → 反转负控（承重——RED again） → …
- Development work in your project
- SKILL.md covers 复现器四判据（照 diagnosing-bugs Phase…, Procedure, 输出契约（机器判据按这个复验，别自由发挥格式） and 产出（副作用 oracle，报告里必须给）, plus 2 more sections
- Calls git, node and rg
What it does
Bug Reproduce is an agent skill from Prismer-AI/PrismerCloud. Turn a known bug into a tight, red-capable reproducer, then prove the reproducer locks that bug with a reversal negative control (reintroduce the bug → reproducer must go red again). Use at the start of a bugfix, before theorizing about the cause.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill.json`). Compatibility notes: ["claude-code"]
It sits in Development. It works with Git. The licence is MIT.
When your agent uses it
- Development work in your project
Example prompts
- “/bug-reproduce”
Requirements
- Compatibility (from SKILL.md): ["claude-code"]
- Pre-approved tools (allowed-tools): Bash
Workflow steps
5 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 e5d9444. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitnoderg
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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.
Compatibility
["claude-code"]
From compatibility in the SKILL.md frontmatter.
Context cost
Bug Reproduce loads about 1.7k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 420 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash
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 Prismer-AI/PrismerCloud at commit e5d9444, republished under its MIT licence (© Prismer-AI). 420 words, ~1,678 tokens.
Download SKILL.mdSave it as
.claude/skills/bug-reproduce/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- bug-reproduce
- description
- Turn a known bug into a tight, red-capable reproducer, then prove the reproducer locks that bug with a reversal negative control (reintroduce the bug → reproducer must go red again). Use at the start of a bugfix, before theorizing about the cause.
- allowed-tools
- Bash
- compatibility
- ["claude-code"]
- license
- MIT
- scope
- coding
- metadata.category
- diagnosis
bug-reproduce
把一个已知 bug 变成紧、可变红的复现器（失败测试 / 脚本），然后用反转负控证明这个复现器真的锁住了那个 bug——不是恰好绿着（apc/05 §2 S1 · apc/12 bug-reproduce 行；纪律移植自 built-in diagnosing-bugs 的 Phase 1 复现 loop）。
什么时候用：一个 bugfix task 开工的第一步——在读代码建假设之前。diagnosing-bugs 的铁律：没有一个能对这个 bug 变红的信号，再多盯代码也没用。本 skill 只补 diagnosing-bugs 缺的那一环：负控——把 fix 撤掉/把 bug 注入回去，复现器必须变红。
铁律：一个复现器只有走完 RED → GREEN → 反转 RED 才算数。只到 GREEN 不算——一个无论 bug 在不在都绿的"复现器"是开卷考试，不是复现（apc/12 §0 负控纪律）。
复现器四判据（照 diagnosing-bugs Phase 1 完成标准）
一个复现器必须是：
| 判据 | 含义 |
|---|---|
| red-capable | 它驱动真正的 bug 代码路径、断言用户描述的确切症状——能对这个 bug 变红，修好后变绿。不是"没崩就算过"。 |
| deterministic | 同一输入每次同一结论（非确定 bug：钉时间/种 RNG/隔离 FS，把复现率拉到可调试）。 |
| fast | 秒级不是分钟级。 |
| agent-runnable | 你能无人值守跑；一条命令（脚本/测试/curl）能贴出调用 + 输出。 |
Procedure
1. 钉环境 + 建复现器（RED）
在一个干净的、确定性的 workspace 里写出最小失败测试/脚本，然后跑它，看它变红：
d=.e2e-tmp/apc/bug-reproduce && rm -rf "$d" && mkdir -p "$d" # repo-relative，已在 .gitignore
# …在 "$d" 里写 subject + repro…
node "$d"/repro.mjs; echo "exit=$?" # 或 apc test --tier=<T> --json / pytest / go test …隔离场景的临时目录用 repo-relative 的 .e2e-tmp/…，不要用 mktemp -d：复现器本身就是证据，判据在你跑完之后把你引用的 path:line 读回磁盘——/tmp 从仓库根不可解析、收尾 rm -rf 更是把唯一产物销毁（test204「证据销毁反 pattern」的同一个坑）。本地真仓库里的 bug 则直接在真路径上做。
- 复现器必须断言用户描述的症状本身（
clamp(-5,0,10)应得 0 而非 -5），不是"没抛异常"。 - 记下确切症状：断言消息、错误、非零退出码。这就是 RED。
- 真仓库里的 bug：复现命令可以是选层的
apc test --tier=<T> --json（读exitCode：0绿 ·1SUT 红 ·78env_blocked）。env_blocked 不是复现——是环境红，先apc env doctor。
2. 最小 fix（GREEN）
打最小修复（只改让复现器变绿所需的那一点），重跑复现器，看它变绿（exit=0）。不顺手清理别的——本步只证明"这个 fix 让这个复现器绿"。
3. 反转负控（承重——RED again）
这是本 skill 的命根子。 把 fix 撤掉——把 bug 注入回去，重跑同一条复现器命令：
# 首选：直接编辑源文件，把 buggy 的那一行 body 原样写回去
node "$d"/repro.mjs; echo "exit=$?" # 必须再次 RED（非零退出 / AssertionError）反转手法只有一个首选：直接编辑源文件把 bug 写回去。
⚠️
git stash/git checkout在共享工作树里是有害指令，默认不许用。 本仓库常态是多个并发 session 共用一个 working tree、几百个未提交改动同时在飞——git stash会把别人正在做的改动一起卷走，git checkout <file>会丢掉别人对同一文件的未提交编辑。这类操作不可逆地毁坏他人工作，代价远大于它省下的那一次手工编辑。只有在你独占这个 working tree（自己的 worktree / 一次性容器）且已确认
git status干净时，git stash才是等价手法；否则一律手工反转。反转的语义（把 bug 放回去）才是承重的，用什么手法不是。
- 复现器必须再次变红。 这证明它红在这个 bug 上，不是恒绿的摆设。
- 若撤掉 fix 后复现器仍然绿 → 复现器是假的，任务失败（
apc/12bug-reproduce 负控）。不许放松断言让它"看起来锁住了"。
4. 恢复 + 收尾（不要删证据）
把 fix 放回去，确认最后一次 GREEN（exit=0）。复现器留在盘上别删——判据是在你跑完之后才读盘复核你引用的行的，rm -rf 掉复现器 = 自毁唯一产物。
5. 写 BugfixCard（repro 阶段）
复现 + 反转都拿到证据后，把这一阶段落成一张 BugfixCard——repro 是 BugfixCard 的首阶段，段锚是 <h2 id="stage-repro">（src/lib/apc-cards/card-profile.ts 的 BUGFIX_STAGES[0].name = 'repro'）。
⚠️ 段名是
repro，不是reproduce。docs/apc/12那行写的stage-reproduce在实现里不存在，写成它会被card-stage-invalid/card-stage-section-missing挡下。以代码为准。
cardfrontmatter：{ kind: 'bugfix', stage: 'repro', taskId: <真 task id>, schemaRev: 1 }——taskId必填，无 task 上下文时不要伪造绑定：如实报告"本轮没有 task，卡未写"，别硬造一张。repro阶段的证据要求是asset：段内要有prismer://…/asset/<id>链接，挂复现器本体 + RED 输出 + 反转 RED 输出三份证据（先cloud asset upload拿 id）。- 段序检查只对已过阶段要求证据，当前阶段进行中不强求；但首阶段段锚
stage-repro必须在场。
Show full SKILL.md (180 more words)Show less
输出契约（机器判据按这个复验，别自由发挥格式）
旧判据全是关键词匹配（"报告里出现过 node/assert/exit=1/revert 这些词"）——一篇一条命令都没跑过的报告照样满分。现在多一条判据（cited-evidence）把复现器读回磁盘复核：复现器不存在、引用的行不存在、或者引用的行根本不含被测符号，当场判红。
① 复现器锚点声明（一行；符号会被复核确实出现在该文件里）：
CHANGE-POINT: <被测符号> @ <复现器/被测文件的 repo-relative 路径>② RED→GREEN→反转 RED 相位表（markdown 表，首列是 path:line）：每相位一行，首列是该相位转在哪一行上。判据要求 ≥3 行带可复核引用，且 ≥2 条引用所在的那一行真的含被测符号。
| path:line | phase | command | exit | observed |
| --- | --- | --- | --- | --- |
| .e2e-tmp/apc/bug-reproduce/repro.mjs:3 | 1 RED (buggy) | node .e2e-tmp/apc/bug-reproduce/repro.mjs | 1 | AssertionError: clamp must respect lower bound |
| .e2e-tmp/apc/bug-reproduce/clamp.mjs:1 | 2 GREEN (fixed) | node .e2e-tmp/apc/bug-reproduce/repro.mjs | 0 | REPRO OK |
| .e2e-tmp/apc/bug-reproduce/repro.mjs:3 | 3 REVERSAL RED | node .e2e-tmp/apc/bug-reproduce/repro.mjs | 1 | AssertionError: clamp must respect lower bound |行号照抄 cat -n / rg -n 的真实输出，不许凭印象写。引用必须 repo-root-relative（绝对路径与 /tmp/... 一律判红——这也是上面要求复现器落 .e2e-tmp/ 且不删的原因）。产物存可引用的扩展名：引用解析器只认固定后缀集（ts/tsx/js/jsx/mjs/cjs/prisma/sql/md/json/sh/py/yml/yaml），存成 .txt/.log 的引用不会被解析。
产出（副作用 oracle，报告里必须给）
- 复现器命令：你真跑过的那一条（
node repro.mjs/apc test --tier=…/ pytest…），可贴调用。 - 初始 RED：buggy 代码下复现器失败（AssertionError + 非零退出码）。
- fix 后 GREEN：
exit=0。 - 反转 RED（承重）：把 bug 注入回去后复现器再次变红（非零退出码）——这是"锁住了"的唯一证明。
- 复现器本体留在盘上（repo-relative 路径），锚点声明 + 相位表的每条引用都能读回。
6.（有 task 上下文时）BugfixCard
stage-repro段：三份证据 asset link 挂上，卡可回读。
不许：只报到 GREEN 就收工（没有反转 = 没证明锁住）；放松断言让恒绿脚本冒充复现器；把 env_blocked（exit 78）当作 bug 复现上报；凭推理宣称"应该能复现"而没真跑；跑完 rm -rf 掉复现器（证据必须留到判据读盘之后）；在共享工作树里用 git stash/git checkout 做反转（会卷走别人的未提交改动）。
诚实边界
- 本 skill 不保证任何 bug 都能建出紧复现器：跨进程时序、真机才暴露、非确定性极低复现率的 bug，可能只能拉高复现率而非稳定复现（
diagnosing-bugsPhase 1）。建不出就显式停手说清楚、列出试过什么、要人给可复现环境/捕获产物——不许无复现器就跳去建假设。 - 反转负控证明的是"复现器红在这个 bug 上"，不是"这个 fix 是最终正解"——正解由后续 fix + 评审 + test-runner 兜。
- 共享工作树是常态：本仓库经常多个 session 同时在同一个 working tree 上飞着几百个未提交改动。因此反转 fix 默认手工编辑源文件；
git stash/git checkout只在你确认独占该工作树、且git status干净时才等价可用。这不是洁癖——stash 卷走别人的改动是不可逆的破坏。 - BugfixCard 的段名以实现为准（
repro）：docs/apc/12里写的stage-reproduce是文档漂移，代码src/lib/apc-cards/card-profile.ts的 BugfixCard 首阶段叫repro。无PRISMER_TASK_ID时card.taskId无法合法填写——如实报告"卡未写"，不要伪造一个绑定去凑一张卡。
<!-- APC-ACK:v1 -->调用回执（APC 平台方运营纪律 · 自动注入，勿手改）
执行本 skill 的第一步，先落一条调用回执：
cloud skill ack bug-reproduce --task "$PRISMER_TASK_ID"按退出码分流（这条命令的退出码是承重信息，禁止用 || 兜底、; true、
set +e 或重定向把它抹掉）：
| exit | 含义 | 你要做的 |
|---|---|---|
0 | 回执已落库（im_task_logs.action='skill_ack'） | 继续执行本 skill |
3 | 无 task 上下文——本次运行没有 task，产不出回执 | 继续执行本 skill；但本次运行没有回执，任何报告里都不得声称已 ack |
4 | 你不是该 task 的 assignee，服务端拒绝 | 停下并上报：回执只能由执行该 task 的 agent 产生 |
1 | 其它失败（网络 / 服务端） | 重试一次；仍失败则继续执行，并在结果里显式标注「回执缺失」 |
回执只证明本 skill 被调度，不证明执行正确——效果证明由本 skill 自己的 acceptanceCriteria 副作用断言承担（apc/04 §2 层 1 诚实标注）。
<!-- /APC-ACK:v1 -->© Prismer-AI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in sdk/apc/skills/bug-reproduce of Prismer-AI/PrismerCloud.
- SKILL.md
- skill.json
Open the folder on GitHubat commit e5d9444
Compare with similar skills
Bug Reproduce 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 |
|---|---|---|---|---|---|---|
| Bug Reproduce this skillPrismer-AI/PrismerCloud | 1.6k | — | ~1.7k | Automated safety check: Notes | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Finishing A Development Branchfarm-fe/farm | 5.6k | 35 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Migrate Internal Package into GhostTryGhost/Ghost | 56k | — | ~3.8k | Automated safety check: Pass | MIT |
Similar skills
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
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.
Finishing A Development Branch
farm-fe/farm
A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
- Official
Doc Sync
JetBrains/ideavim
Keeps IdeaVim documentation in sync with code changes. An agent skill from JetBrains/ideavim.
More from Prismer-AI/PrismerCloud
All 88 skills in this repoPrismer Google Workspace
Prismer-AI/PrismerCloud
Gives an agent account-scoped access to Gmail, Calendar, Drive, Contacts, Docs and Sheets through the gws CLI or a bundled Python client.
Prismer Skill Creator
Prismer-AI/PrismerCloud
Walks an agent through creating, importing, editing, validating, testing and publishing Prismer Skills with a fixed workflow and bundled scripts.
Himalaya Email CLI
Prismer-AI/PrismerCloud
Operates a mailbox from the terminal with the external Himalaya CLI over IMAP, SMTP, Notmuch or Sendmail, separate from any built-in email gateway adapter.
Prismer Image Generation
Prismer-AI/PrismerCloud
Generates one image from a text prompt with a bundled Node.js helper and delivers it once as the attachment to the current Prismer reply.
Manim Explainer Videos
Prismer-AI/PrismerCloud
Produces 3Blue1Brown-style explainer animations with Manim Community Edition for math, algorithms, equations and architecture diagrams, with planning and rendering references.
Prismer Role Builder
Prismer-AI/PrismerCloud
Creates or updates Prismer role templates from a persona, SOP or job description, and turns a role into a working agent that runs its first task through a bundled script.
Related
Works with
Categories
Questions about Bug Reproduce
What does Bug Reproduce do?
Turn a known bug into a tight, red-capable reproducer, then prove the reproducer locks that bug with a reversal negative control (reintroduce the bug → reproducer must go red again). Bug Reproduce is an agent skill from Prismer-AI/PrismerCloud. Turn a known bug into a tight, red-capable reproducer, then prove the reproducer locks that bug with a reversal negative control (reintroduce the bug → reproducer must go red again).
When should I use Bug Reproduce?
Bug Reproduce fits situations like: development work in your project.
How do I install Bug Reproduce in Claude Code?
Run `npx skills add Prismer-AI/PrismerCloud --skill bug-reproduce -a claude-code`. Or copy the skill folder (sdk/apc/skills/bug-reproduce in Prismer-AI/PrismerCloud) into .claude/skills/bug-reproduce in your project. Claude Code loads it when a task matches its description.
How do I install Bug Reproduce in Codex?
Run `npx skills add Prismer-AI/PrismerCloud --skill bug-reproduce -a codex`. Or copy the skill folder (sdk/apc/skills/bug-reproduce in Prismer-AI/PrismerCloud) into .agents/skills/bug-reproduce in your project. Codex loads it when a task matches its description.
Can I use Bug Reproduce 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 Prismer-AI/PrismerCloud --skill bug-reproduce -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bug-reproduce, .gemini/skills/bug-reproduce, .github/skills/bug-reproduce and .opencode/skills/bug-reproduce in your project.
What does Bug Reproduce need to run?
Going by SKILL.md and its folder, Bug Reproduce needs the command-line tools its instructions call (git, node and rg). Its frontmatter pre-approves these tools: Bash. Compatibility (from SKILL.md): ["claude-code"].
Does Bug Reproduce access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Bug Reproduce safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Bug Reproduce use?
Bug Reproduce is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Bug Reproduce use?
About 1.7k tokens (SKILL.md is roughly 6.7k 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 Bug Reproduce?
Skills that share tags, products or a category with Bug Reproduce: Finishing a Development Branch (obra/superpowers, 297k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Finishing A Development Branch (farm-fe/farm, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Bug Reproduce?
Prismer-AI (a GitHub organization) maintains it in Prismer-AI/PrismerCloud, which has 1,555 GitHub stars. The repository holds 88 skills in this directory. The repository was last updated on September 30, 2026.
Source: Prismer-AI/PrismerCloud on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.