Pr To Main

This automates the full PR workflow for a pnpm monorepo that uses Changesets for versioning. It figures out which packages changed, makes sure you have a changeset file (or creates one), runs the build to catch breaks early, then opens a PR with the right template and conventional commit title. The key insight is that Changesets-driven repos need a .changeset/*.md file in every release-worthy PR or the change never ships, so this enforces that before you even get to review. Built for a Japanese/English team (responds to "PRを作成"), but the PR itself always comes out in English per repo rules. Saves you from the "merged but never released" trap.

GitHub stars: 5.1K
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add breaking-brake/cc-wf-studio --skill pr-to-main --agent claude-code

Installs into .claude/skills of the current project.

Files

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

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