Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
Opens a pull request to main in a pnpm and Changesets monorepo, after working out which packages changed and making sure a changeset file exists.
Install Changesets Pull Request to Main
$ npx skills add breaking-brake/cc-wf-studio --skill pr-to-main -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install breaking-brake/cc-wf-studio pr-to-main --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/pr-to-main .claude/skills/pr-to-main && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pr-to-main" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/pr-to-main into .claude/skills/pr-to-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-to-main", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/pr-to-mainType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add breaking-brake/cc-wf-studio --skill pr-to-main -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install breaking-brake/cc-wf-studio pr-to-main --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/pr-to-main .agents/skills/pr-to-main && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pr-to-main" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/pr-to-main into .agents/skills/pr-to-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-to-main", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add breaking-brake/cc-wf-studio --skill pr-to-main -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install breaking-brake/cc-wf-studio pr-to-main --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/pr-to-main .cursor/skills/pr-to-main && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pr-to-main" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/pr-to-main into .cursor/skills/pr-to-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-to-main", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/breaking-brake/cc-wf-studio.git --path .claude/skills/pr-to-main--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add breaking-brake/cc-wf-studio --skill pr-to-main -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install breaking-brake/cc-wf-studio pr-to-main --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/pr-to-main .gemini/skills/pr-to-main && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pr-to-main" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/pr-to-main into .gemini/skills/pr-to-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-to-main", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install breaking-brake/cc-wf-studio pr-to-mainInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add breaking-brake/cc-wf-studio --skill pr-to-main -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/pr-to-main .github/skills/pr-to-main && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pr-to-main" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/pr-to-main into .github/skills/pr-to-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-to-main", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add breaking-brake/cc-wf-studio --skill pr-to-main -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install breaking-brake/cc-wf-studio pr-to-main --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/pr-to-main .opencode/skills/pr-to-main && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pr-to-main" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/pr-to-main into .opencode/skills/pr-to-main/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-to-main", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pr-to-main- GitHub stars
- 5.4k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 662 words
- Files
- 4 (incl. assets)
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Opens a pull request to main in a pnpm and Changesets monorepo, after working out which packages changed and making sure a changeset file exists.
- Works in 6 steps: Gather context (run in parallel) → Identify scope and type → Ensure a changeset exists (the… → …
- Submitting a feature or fix branch for review against main
- SKILL.md covers Workflow, PR Format and Templates
- Calls git, pnpm and gh
What it does
Written for the cc-wf-studio monorepo, which has four packages (core, mcp, cli and vscode) and releases through Changesets instead of commit messages. A change that should ship needs a `.changeset/*.md` file in the same pull request, otherwise it merges but is never released. So the agent does more than open a PR: it gathers context with `git status`, the diffs against origin/main, the branch's commit log and a look at the `.changeset` folder.
Next it maps the changed paths to packages, such as `packages/core` to `@cc-wf-studio/core` and `packages/vscode` to the `cc-wf-studio` extension, and reads the commit prefixes (fix, feat, improvement) across the whole branch. If a release is needed and no changeset exists, it creates one with `pnpm changeset`, picking the package and a patch, minor or major bump and writing a one-line summary for the changelog. Changes that need no release, such as CI-only, tooling or docs, get an empty changeset from `pnpm changeset add --empty`. Three template files in `assets` cover feature, fix and improvement pull requests.
When your agent uses it
- Submitting a feature or fix branch for review against main
- Checking whether a change needs a changeset and which package it belongs to
- Writing the changeset summary that becomes the changelog entry
- Marking a docs or CI-only change as needing no release
Example prompts
- “Open a PR to main for my fix in packages/vscode.”
- “Create the pull request for this branch and add a minor changeset for the core package.”
- “This branch only touches the .github workflows; add an empty changeset and open the PR.”
Requirements
- A pnpm monorepo that uses Changesets
- A Git branch with an origin/main to compare against
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Gather context (run in parallel)
- Identify scope and type
- Ensure a changeset exists (the monorepo-critical step)
- Verify the build is green before opening the PR
- Select the PR template based on type (from step 2)
- Create the PR
What it can do on your machine
Read from SKILL.md and the folder at commit a7bf24a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitpnpmgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, pnpm and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Changesets Pull Request to Main loads about 1.4k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 662 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 662 words (~1,351 tokens).
“Create a PR for a feature/fix branch targeting main in the cc-wf-studio monorepo.”
- name
- pr-to-main
Files
SKILL.md and 3 other files (assets) in .claude/skills/pr-to-main of breaking-brake/cc-wf-studio.
- SKILL.md
- assets/feat-template.md
- assets/fix-template.md
- assets/improvement-template.md
Open the folder on GitHubat commit a7bf24a
Compare with similar skills
Changesets Pull Request to Main next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Changesets Pull Request to Main this skillbreaking-brake/cc-wf-studio | 5.4k | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| ZCF Release AutomationUfoMiao/zcf | 6.1k | — | ~3.4k | Automated safety check: Pass | MIT | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Git Workflow and Versioningaddyosmani/agent-skills | 104k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| pybind11 Release Preparationpybind/pybind11 | 18k | — | ~1.7k | Automated safety check: Pass | Custom licence |
Similar skills
ZCF Release Automation
UfoMiao/zcf
Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
pybind11 Release Preparation
pybind/pybind11
Opens the pybind11 release-preparation pull request: picking the release base, bumping the version in common.h and integrating the changelog, following docs/release.rst.
AionUi Version Bump
iOfficeAI/AionUi
Automates an AionUi release: checks the latest AionCore release and its artifacts, updates package.json, writes the changelog, opens a PR and tags the release.
More from breaking-brake/cc-wf-studio
All 11 skills in this repoCC Workflow Studio AI Editor
breaking-brake/cc-wf-studio
Creates and edits visual agent workflows in CC Workflow Studio through conversation, with the agent reading and writing the canvas over MCP.
PR Review Analysis
breaking-brake/cc-wf-studio
Fetches review comments from a GitHub pull request, checks each one against the real code, rates it valid, invalid or partial, and can reply on GitHub.
Workflow Schema Tuning
breaking-brake/cc-wf-studio
Guides edits to cc-wf-studio's workflow schema so AI agents generate better workflows, treating schema text as prompt engineering rather than validation.
PR Merge Branch Cleanup
breaking-brake/cc-wf-studio
Clean up merged feature branches after PR to main is merged. Use when the user says "ブランチ削除", "cleanup", "マージ後の片付け", or wants to delete a merged branch.
ccwf Workflow CLI
breaking-brake/cc-wf-studio
Teaches the agent to use the ccwf command line tool to validate, preview, render, export and run cc-wf-studio workflow JSON files without opening VS Code.
Next Idea Ideation Loop
breaking-brake/cc-wf-studio
Runs one unattended ideation round for cc-wf-studio: orient on plans and issues, invent user-visible improvements, judge them against a value bar and file the winners as locked idea issues.
Related
Categories
Questions about Changesets Pull Request to Main
What does Changesets Pull Request to Main do?
Opens a pull request to main in a pnpm and Changesets monorepo, after working out which packages changed and making sure a changeset file exists. Written for the cc-wf-studio monorepo, which has four packages (core, mcp, cli and vscode) and releases through Changesets instead of commit messages.md` file in the same pull request, otherwise it merges but is never released.
When should I use Changesets Pull Request to Main?
Changesets Pull Request to Main fits situations like: submitting a feature or fix branch for review against main; checking whether a change needs a changeset and which package it belongs to; writing the changeset summary that becomes the changelog entry; marking a docs or CI-only change as needing no release.
How do I install Changesets Pull Request to Main in Claude Code?
Run `npx skills add breaking-brake/cc-wf-studio --skill pr-to-main -a claude-code`. Or copy the skill folder (.claude/skills/pr-to-main in breaking-brake/cc-wf-studio) into .claude/skills/pr-to-main in your project. Claude Code loads it when a task matches its description.
How do I install Changesets Pull Request to Main in Codex?
Run `npx skills add breaking-brake/cc-wf-studio --skill pr-to-main -a codex`. Or copy the skill folder (.claude/skills/pr-to-main in breaking-brake/cc-wf-studio) into .agents/skills/pr-to-main in your project. Codex loads it when a task matches its description.
Can I use Changesets Pull Request to Main in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add breaking-brake/cc-wf-studio --skill pr-to-main -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-to-main, .gemini/skills/pr-to-main, .github/skills/pr-to-main and .opencode/skills/pr-to-main in your project.
What does Changesets Pull Request to Main need to run?
Going by SKILL.md and its folder, Changesets Pull Request to Main needs the command-line tools its instructions call (git, pnpm and gh). Our summary lists: A pnpm monorepo that uses Changesets; A Git branch with an origin/main to compare against.
Does Changesets Pull Request to Main access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Changesets Pull Request to Main safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Changesets Pull Request to Main use?
Changesets Pull Request to Main has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Changesets Pull Request to Main use?
About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Changesets Pull Request to Main?
Skills that share tags, products or a category with Changesets Pull Request to Main: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), ZCF Release Automation (UfoMiao/zcf, 6.1k stars), React Router Release Notes Prep (remix-run/react-router, 57k stars) and Git Workflow and Versioning (addyosmani/agent-skills, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Changesets Pull Request to Main?
breaking-brake (a GitHub user) maintains it in breaking-brake/cc-wf-studio, which has 5,394 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.
Source: breaking-brake/cc-wf-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.