" --body "<body>"`. 9. After creating PR, run `gh pr diff <number> --name-only` and `gh pr view <number> --json files,title,body` to confirm body matches actual changed files. ## Before creating a develop → main release PR 1. Run `git fetch origin`. 2. Run `git diff origin/main...origin/develop --name-status` to see actual release contents. 3. Run `git log --oneline origin/main..origin/develop` to review Conventional Commits that release-please will see after merge. 4. Verify release PR body summarizes the diff, not stale branch history. 5. Create PR: `gh pr create --base main --head develop --title "chore(release): merge develop into main" --body "<body>"`. 6. Merge with a merge commit, not squash. ## Title quality check - [ ] Would a user reading the changelog understand what changed? - [ ] Does it cover all user-visible changes, not just the first commit? - [ ] Is the type correct? (feat = user-visible feature, fix = bug, chore = internal) - [ ] No period at the end. No trailing punctuation. ## Bad vs Good Bad: `feat: updates` (vague) Bad: `fix: typo in readme` when the branch also adds tests and error handling (understates) Bad: `feat: add error handling, tests, --version flag, npm publish, CONTRIBUTING.md` (too long, use body) Good: `feat: add error handling, tests, and npm publish workflow` (concise, accurate scope) Good: `fix: handle malformed JSONL in source parsers` (specific, covers the real fix) --- > Source: [PanAchy/copilot-arewecooked](https://github.com/PanAchy/copilot-arewecooked) — distributed by [TomeVault](https://tomevault.io). <!-- tomevault:4.0:skill

# Create Pr > Create PRs with titles and bodies that produce accurate release notes. Use when opening a pull request, merging to develop or main, or when user says "open a PR", "create a PR", "ready to merge", or "ship it". Use when this capability is needed. - Skill: `tomevault-io/create-pr-34` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/create-pr-34` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/create-pr-34/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/create-pr-34 --- # Create PR ## Rules 1. Create short-lived feature branches from `develop` for all work. 2. Open normal work PRs from feature branches into `develop`. 3. Prefer squash merge for feature → develop PRs. The PR title becomes one clean Conventional Commit on `develop`. 4. Open release PRs from `develop` into `main` when ready to ship. 5. Merge release PRs with a merge commit, not squash, so release-please sees the individual Conventional Commits accumulated on `develop`. 6. The release PR body becomes useful release context, but release-please changelog entries come from commits merged to `main`. 7. Use `fix(...)` for release-affecting fixes, including broken publish/release automation. Do not use `ci(...)` if the change must trigger a release. ## PR title format ``` ():

``` Pick the highest-impact type: `feat` > `fix` > `refactor` > `test` > `docs` > `chore`. ## PR body format ``` ## What changed - - - ## Context <1-2 sentences on why> ## Test plan - [ ] ``` ## Before creating a feature → develop PR 1. Run `git fetch origin`. 2. Confirm current branch is a feature branch, not `main` or `develop`: `git branch --show-current`. 3. Run `git diff origin/develop...HEAD --name-status` to see actual changed files in the PR. 4. Run `git diff origin/develop...HEAD -- ` to understand actual content changes. 5. Synthesize the title and body from the diff, not from commit headlines alone. 6. Verify `npm run build && npm test` passes. 7. Push the branch: `git push -u origin `. 8. Create PR: `gh pr create --base develop --head --title "" --body "<body>"`. 9. After creating PR, run `gh pr diff <number> --name-only` and `gh pr view <number> --json files,title,body` to confirm body matches actual changed files. ## Before creating a develop → main release PR 1. Run `git fetch origin`. 2. Run `git diff origin/main...origin/develop --name-status` to see actual release contents. 3. Run `git log --oneline origin/main..origin/develop` to review Conventional Commits that release-please will see after merge. 4. Verify release PR body summarizes the diff, not stale branch history. 5. Create PR: `gh pr create --base main --head develop --title "chore(release): merge develop into main" --body "<body>"`. 6. Merge with a merge commit, not squash. ## Title quality check - [ ] Would a user reading the changelog understand what changed? - [ ] Does it cover all user-visible changes, not just the first commit? - [ ] Is the type correct? (feat = user-visible feature, fix = bug, chore = internal) - [ ] No period at the end. No trailing punctuation. ## Bad vs Good Bad: `feat: updates` (vague) Bad: `fix: typo in readme` when the branch also adds tests and error handling (understates) Bad: `feat: add error handling, tests, --version flag, npm publish, CONTRIBUTING.md` (too long, use body) Good: `feat: add error handling, tests, and npm publish workflow` (concise, accurate scope) Good: `fix: handle malformed JSONL in source parsers` (specific, covers the real fix) --- > Source: [PanAchy/copilot-arewecooked](https://github.com/PanAchy/copilot-arewecooked) — distributed by [TomeVault](https://tomevault.io).