菜单
Stage, commit, and (when a remote exists) push changes with a well-formed Conventional Commits message.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
A disciplined workflow for tracing hard / stubborn bugs in the 5thPlanet Saturn emulator without tunnel-visioning — classify the failure, make it deterministic, write the hypothesis with explicit falsification, win by register-completeness + an EARLY oracle diff, instrument the transform's OUTPUT, ALWAYS fan out to multiple parallel agents with competing hypotheses, and run a self-check tripwire when probes stop narrowing. Use it for LLE fidelity gaps (render / audio / timing / boot), intermittent stalls, "random" crashes, and any bug where the first few probes haven't eliminated a cause.
Dump a physical SEGA Saturn game disc to a 5thPlanet-loadable CUE-BIN image, using redumper (preferred) or cdrdao (handling its MSB-first CD-DA byte-swap gotcha).
Manage the full software release process for the 5thPlanet workspace — version bumps, changelogs, Git tags, and (when applicable) GitHub releases.
Perform a project-wide code review of the 5thPlanet SEGA Saturn emulator, covering correctness, emulation accuracy, code quality, tests, documentation, and style.
Audit and update all project documentation to stay in sync with the current development status of the 5thPlanet SEGA Saturn emulator.
Profile and analyze the performance of the 5thPlanet SEGA Saturn emulator end-to-end — from the SH-2 interpreter core through the VDP2 compositor to the SDL2 jupiter frontend — then report concrete, accuracy-safe optimization opportunities.
| name | commit-and-push |
| description | Stage, commit, and (when a remote exists) push changes with a well-formed Conventional Commits message. |
When committing and pushing changes, always follow these steps:
Verify tests pass — run cargo test --workspace before committing. A red bar must not be committed. If a test is intentionally being marked #[ignore] or #[should_panic], call it out in the commit body.
Stage all relevant changes with git add <paths>. Be deliberate — stage only files related to the current topic. Never blindly use git add -A if unrelated changes are present.
Compose the message following the Conventional Commits standard. Use these scopes for this project:
sh2 — anything inside crates/sh2/saturn — anything inside crates/saturn/jupiter — jupiter/ frontend binaryworkspace — root Cargo.toml, .gitignore, shared lintsdoc — doc/**, README.md, CLAUDE.mdci — .github/, hooks, scriptsfeat, fix, refactor, test, docs, chore as the type.The message should explain why the change was made, not just what changed. When the change advances a task in doc/roadmap.md, reference the task number (e.g. "advances M1 task #4").
Commit with the composed message.
Push the committed changes to the current branch on the remote — but only if a remote is configured. Check with git remote -v first. If no remote exists, stop here and report the local commit hash; do not invent or add a remote without the user's explicit instruction.
Verify that the push succeeded and the remote is in sync with the local branch (git status should report "up to date").