mit einem Klick
ci-pr-helper
// Run local test/style checks and open GitHub PRs for lance-context. Use when asked to run CI-equivalent checks (uv pytest, ruff/pyright, cargo fmt/clippy/test) and then create a PR with a proper title/body.
// Run local test/style checks and open GitHub PRs for lance-context. Use when asked to run CI-equivalent checks (uv pytest, ruff/pyright, cargo fmt/clippy/test) and then create a PR with a proper title/body.
| name | ci-pr-helper |
| description | Run local test/style checks and open GitHub PRs for lance-context. Use when asked to run CI-equivalent checks (uv pytest, ruff/pyright, cargo fmt/clippy/test) and then create a PR with a proper title/body. |
Run project checks locally, then prepare and open a PR with a clear title and summary.
main).scripts/.gh is available and authenticated, run gh pr create yourself; otherwise, surface the exact command for the user to execute manually.Run:
./.codex/skills/ci-pr-helper/scripts/run_ci_checks.sh
If it fails due to missing tools, install uv, cargo, or Python deps, then rerun.
Draft a conventional title (e.g., feat:/fix:/ci:) and use:
## Summary
- ...
## Testing
- uv run pytest
- cargo test --manifest-path rust/lance-context/Cargo.toml
- cargo fmt --manifest-path rust/lance-context/Cargo.toml -- --check
- cargo clippy --manifest-path rust/lance-context/Cargo.toml --all-targets -- -D warnings
- ruff format --check python/
- ruff check python/
- pyright
If you need to check auth status, you may still run:
gh auth status
When ready:
gh is ready to use, execute:gh pr create --title "<title>" --body "<body>"
Some environments emit a spurious Unsupported subcommand 'pr' warning before running
gh; ignore that message and continue with the command.
If gh is missing or fails, print the command instead so the user can run it locally.