pr

The skill detects the base branch automatically: it targets homolog when that branch exists locally or on origin, and falls back to main otherwise. If your branch is behind the base, it rebases and pushes with --force-with-lease before opening the PR.

Write the body to a file with the Write tool containing Summary, Changes, Technical Notes, Test Plan, and References sections, then run gh pr create with --body-file as a separate command. Combining file creation and gh pr create in one command fails because the validation hook reads the file before the command runs.

No, PRs never target main directly under the enforced feature/* → homolog → main flow. Only a PR opened from the homolog branch itself targets main, and repositories without a homolog branch fall back to main as the base.

The bravros police PreToolUse hook validates the body file before the command executes, so a heredoc or chained cat-and-create command means the file does not exist at validation time and gets blocked. Write the body file in a separate prior tool call instead.

Yes, it checks repo visibility with gh repo view and strips any AI-attribution footer such as Generated-with lines or Co-Authored-By trailers from the body file before creating the PR. On public repos such footers are treated as an information leak.

The skill always hands off to review: interactively it invokes the pr-review skill immediately, and in autonomous mode it prints a STATUS line with the PR number so the pipeline triggers review. Creating the PR without the handoff is considered unfinished work.