Menu
Fix a GitHub issue with proper branch, testing, and PR workflow
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Build and test the libuipc project using XMake. Use when building with xmake, running xmake f / xmake build / xmake run commands, selecting release/releasedbg/debug modes, or running Catch2 tests produced by xmake.
Build and test the libuipc project using CMake. Use when building the project, running cmake configure/build commands, compiling with RelWithDebInfo, running Catch2 tests, or when the user asks how to build or test libuipc.
General simulation development best practices for correctness, stability, and debuggability. Use when implementing or modifying simulation systems, solvers, constraints, or GPU kernels, especially for index safety, NaN/Inf issues, and diagnostics.
Review a libuipc pull request end-to-end: checkout the PR, summarize changes, list files for the human reviewer, and perform a domain-aware AI review covering physics correctness, backend architecture, C++ style, GPU code, and Python bindings. Optionally post review comments via `gh`. Use when the user provides a PR number, asks to review a PR, or wants to inspect a libuipc GitHub PR.
Push a version tag and optionally create a GitHub release
Conventional commit message format and rules for this project
| name | fix-issue |
| description | Fix a GitHub issue with proper branch, testing, and PR workflow |
| disable-model-invocation | true |
If no issue number is provided, list and ask the developer to pick:
gh issue list --repo spiriMirror/libuipc
gh issue view <ISSUE_NUMBER> --repo spiriMirror/libuipc
Note: Always use --repo spiriMirror/libuipc to reference the upstream repository (works with forks). See repository-setup.mdc for details.
Determine the issue type: bug fix, feature, performance, refactor, docs, or test improvement.
git checkout -b fix/issue-<ISSUE_NUMBER>
Use feat/ prefix for features, fix/ for bugs, refactor/ for refactoring, etc.
Switch to plan mode. Analyze the issue, identify root cause, then implement the fix.
Build with the build command.
<cmake-binary-directory>/<configuration>/bin/.apps/tests/.Add new tests in apps/tests/ when the bug isn't covered by existing tests.
Rules:
Use the commit command to format, commit, and push.
Switch to review mode, review all changes, then create a PR via github-pr.md.