Skip to main content
The PR surface is two-step by design. Finding commands write a JSON handoff; pikopod pr consumes it. Credentials come from the environment or the gh CLI, never from a flag.

Post a comment

One marker-tagged comment per finding source, updated in place on re-runs rather than a new comment per run. The comment carries the head SHA, so a stale comment is visible as such. Handoffs come from spec-diff, replay --ci, conformance and spec-update. If the token cannot comment, as with a read-only token on a pull request from a fork, pr comment writes the report to the job summary instead, or to stdout, and exits 0 with a note on stderr.

Open a pull request

pr open branches, commits the files you name, pushes, and opens a PR whose body is the handoff rendered as evidence. --dry-run prints the git and PR plan without executing. Branch names may not start with -. pikopod fix --pr uses the same machinery with its own body. See Fix.

Platforms and credentials

Repository, pull request number and head SHA default from the CI environment. Outside CI, pass --platform github|gitlab, --repo owner/name (or the GitLab project path or id), --number <pr> for comments, and --api <url> for GitHub Enterprise or self-hosted GitLab. See Environment variables.