pr-to-main
Create 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.
npx skills add breaking-brake/cc-wf-studio --skill pr-to-main --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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/*.md` file 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 1. **Gather context** (run in parallel): - `git status` (no `-uall`) - `git diff` (staged + unstaged) and `git diff origin/main...HEAD` for the full branch delta - `git log origin/main..HEAD --oneline` for every commit on the branch - Check whether the branch tracks a remote and needs pushing - `ls .changeset/*.md` to see whether a changeset already exists 2. **Identify scope and type**: - **Affected package(s)**: map changed p
- Workflow
- PR Format
- Templates
What does the pr-to-main skill do?
Create 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.
How do I install it?
Run `npx skills add breaking-brake/cc-wf-studio --skill pr-to-main --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From breaking-brake/cc-wf-studio, a repository with 5,342 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.