Create PR
Split independent work into separate PRs and stack dependent work.
Workflow
- Branch. Pushing to
mainneeds explicit permission from the user; everything else goes through a feature branch named after the change (existing branches read<type>/<description>). Commits come from thecommitskill, so they stay atomic and independently revertable. Leave unrelated formatter churn, generated files, and user edits outside the task unstaged. - Push and open the PR —
references/open-pr.md. Use the Conventional Commit scope rules in thecommitskill. - Request and handle AI review —
references/ai-review.md, with theghreply and thread-state calls inreferences/gh-review.md. - Watch CI after opening and after every push with
gh pr checks. Read the failing step logs and annotations rather than the summary, then use thefix-ciskill for the fix, and ask the bots for another pass if they do not rerun on their own. - Merge only when the user explicitly asks and the conditions below hold:
gh pr merge <pr> --squash, without--delete-branchor--body-file. When the PR fixes an issue someone else reported, credit that reporter with aCo-authored-bytrailer on one of the PR's commits before merging, using their noreply address<id>+<login>@users.noreply.github.com(gh api users/<login> --jq .id): the squash body is built from the commit messages. - After merging, reply on each linked issue and on any original contributor PR it superseded. For a branch offered without a PR, reply where it was offered. Say what landed and in which PR, and, when it changes the published package, the release that shipped it or that it ships with the next one. Do this in particular when someone pinged or offered a branch and got no answer.
Ready means
- The branch is pushed, the PR exists, and its body describes the change and the validation that ran.
- CodeRabbit — and Cubic when it is available on the PR — reviewed the latest pushed commit, with no unresolved actionable feedback.
- Every required check passes. Queued, cancelled, failing, or missing required checks all mean not ready.
- The user has the PR URL plus any residual risk or pending external state.
When a bot or CI system stays silent past a reasonable polling window, state exactly what is pending instead of claiming completion, and leave the visible PR comment or CI state for follow-up.
Context
- Reviewer bots act on a comment only when their handle is mentioned — in the initial request and in every reply asking them to do something.
- Amending or force-pushing after reviewers have read the PR needs an explicit request from the user.