Menu
Guide for setting up repository remotes when working with forks
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional 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 | repository-setup |
| description | Guide for setting up repository remotes when working with forks |
When working with a forked repository, GitHub CLI (gh) commands may fail to find issues and PRs because they default to the fork's repository instead of the upstream repository.
Add the upstream repository as a remote (you can name it anything, upstream is conventional):
git remote add upstream https://github.com/spiriMirror/libuipc
All Cursor commands use --repo spiriMirror/libuipc to reference the upstream repository, ensuring they work correctly in:
This ensures issues and PRs are always referenced from the upstream repository where they actually exist.