con un clic
github-pr
Create a well-structured pull request with proper description
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Menú
Create a well-structured pull request with proper description
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
| name | github-pr |
| description | Create a well-structured pull request with proper description |
| disable-model-invocation | true |
Create a well-structured pull request with proper description, labels, and reviewers.
Follow the commit convention for all commit messages and PR titles.
Prepare branch
# Use 'origin' remote (most common), or specify a different remote if needed
git push -u origin HEAD
Create PR
Write the PR description to a temp file first to avoid shell escaping issues:
# Write description to temp file (output/ is gitignored)
mkdir -p output/.cursor
cat > output/.cursor/pr_body.md << 'EOF'
## Summary
...
EOF
# Create the PR - always target upstream repository
gh pr create --title "<type>(<scope>): <summary>" --body-file output/.cursor/pr_body.md --base main --repo spiriMirror/libuipc
# Clean up
rm -r output/.cursor
Note: Always use --repo spiriMirror/libuipc to create PRs against the upstream repository (works with forks).
PR description should include
Fixes #123)After creating
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
Basado en la clasificación ocupacional SOC