breaking-brake/cc-wf-studio / .claude/skills/pr-to-main
pr-to-main
VerifiedCreate a PR to the main branch for feature/fix changes in this pnpm + Changesets monorepo. Use when the user says "PRを作成", "mainにPR", or wants to submit changes for review. Always run this in the monorepo-aware way — identify the affected package(s) and make sure a changeset exists, because the release pipeline is Changesets-driven.
PR to Main Branch
Create a PR for a feature/fix branch targeting main in the cc-wf-studio monorepo.
This is a pnpm monorepo with four packages (packages/core, packages/mcp, packages/cli, packages/vscode) and versioning is driven by Changesets, not commit messages. Two monorepo facts shape this workflow:
- A release-worthy change must ship with a
.changeset/*.mdfile in the same PR. Without it, the change merges but never gets released — and pending changesets later block promotion to production. - Knowing which package(s) changed drives the changeset target, the PR scope, and the commit scope (e.g.
fix(vscode):).
So the job here is not just "open a PR" — it's "open a PR that the release pipeline can actually act on."
Workflow
-
Gather context (run in parallel):
git status(no-uall)git diff(staged + unstaged) andgit diff origin/main...HEADfor the full branch deltagit log origin/main..HEAD --onelinefor every commit on the branch- Check whether the branch tracks a remote and needs pushing
ls .changeset/*.mdto see whether a changeset already exists
-
Identify scope and type:
- Affected package(s): map changed paths to packages —
packages/core→@cc-wf-studio/core,packages/mcp→@cc-wf-studio/mcp,packages/cli→@cc-wf-studio/cli,packages/vscode→cc-wf-studio(the VSCode extension). Changes outsidepackages/(root config,.github/, docs) usually need no release. - Type: read the commit prefix, allowing an optional scope —
fix:/fix(vscode):→ fix,feat:/feat(core):→ feat,improvement:→ improvement. Review all commits on the branch, not just the latest.
- Affected package(s): map changed paths to packages —
-
Ensure a changeset exists (the monorepo-critical step):
- If a
.changeset/*.mdalready covers this change, confirm it names the right package(s) and bump level, and move on. - If the change should be released and no changeset exists, create one with
pnpm changeset— select the affected package(s) from step 2, choose patch/minor/major, and write a one-line summary (this becomes the CHANGELOG entry). Note: bumping@cc-wf-studio/coreauto-bumps its dependents, so you don't author separate changesets forcli/mcp. - If the change genuinely needs no release (CI-only, tooling, docs), record that intent explicitly with
pnpm changeset add --emptyso the pipeline isn't left guessing. - Why this matters: releases are cut later by manually opening the Release PR (which consumes the accumulated changesets) and merging it — that merge auto-publishes. A PR that lands without the right changeset silently never gets released. (See
docs/release-flow.mdfor the release side — releasing is a human-only action, not something to self-trigger.)
- If a
-
Verify the build is green before opening the PR:
- Run
pnpm check && pnpm buildfrom the repo root (Biome + type-checks, then full compilation). Reviewers and CI expect a clean tree, and catching breakage now is cheaper than after review.
- Run
-
Select the PR template based on type (from step 2):
fix:→assets/fix-template.mdfeat:→assets/feat-template.mdimprovement:→assets/improvement-template.md
-
Create the PR:
- Push the branch with
git push -uif it has no upstream. - Open it with
gh pr create --base main, filling the chosen template.
- Push the branch with
PR Format
- Language: always write the PR title and body in English (repo rule).
- Title —
mainmerges via squash, so the PR title becomes the squash commit subject. It must therefore follow the commit convention:<type>(<scope>): <description>.<type>: matches the change type from step 2 —fix/feat/improvement/docs/refactor/chore/ci.<scope>: the affected package/area from step 2 —vscode,cli,mcp,core(use the directory name, not the npm name). List several as(cli, mcp). Omit the scope for repo-wide changes (root config,.github/, top-level docs), e.g.ci: guard against pending changesets.<description>: imperative mood, no trailing period, concise (aim ≤50 chars per the commit guideline; GitHub appends a(#NN)suffix, with a leading space, on squash — so don't pad it).- Examples (from this repo's history):
fix(vscode): parse Changesets-format CHANGELOG,feat(cli): ccwf install-skills subcommand,docs: add root README for the monorepo.
- Body: in the Changes section, write real monorepo paths (
packages/vscode/src/...,packages/core/...), not generic placeholders. - Mention the changeset in the body so reviewers can see the intended release effect — e.g. "Adds a
patchchangeset forcc-wf-studio" or "No release needed (empty changeset)".
Templates
- fix:
assets/fix-template.md— Problem/Solution with Current vs Expected behavior. - feat:
assets/feat-template.md— Summary/Motivation/Changes. - improvement:
assets/improvement-template.md— Before/After comparison.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |