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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, highly actionable workflow with concrete commands and clear sequencing. The main gaps are a broken reference to docs/release-flow.md, the absence of an explicit error-recovery loop, and a few trimmable motivational sentences.

Suggestions

Fix or remove the dangling reference to docs/release-flow.md in step 3 — the docs/ directory is not present in the bundle, so this reference currently does not resolve.

Add an explicit build-failure feedback loop to step 4 (e.g. "if pnpm check or pnpm build fails, fix the reported issue and re-run until green") to earn a higher workflow_clarity score.

Trim framing prose such as "So the job here is not just 'open a PR' — it's 'open a PR that the release pipeline can actually act on." to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands throughout; a few motivational sentences ("So the job here is not just 'open a PR' — it's 'open a PR that the release pipeline can actually act on.'") could be trimmed; not a 5 because of these minor over-explanation instances, not a 3 because the bulk is lean.	4 / 5
Actionability	Fully executable guidance with copy-paste-ready commands (git status, git diff, pnpm check && pnpm build, gh pr create --base main), an explicit package-path-to-npm-name mapping, and title examples drawn from real history covering the common cases.	5 / 5
Workflow Clarity	A clear 6-step sequence with an explicit validation checkpoint (step 4: verify build green) and conditional branching in the changeset step; not a 5 because there is no explicit build-failure feedback loop (fix → re-run) and error recovery is only implied.	4 / 5
Progressive Disclosure	Good structure with templates appropriately split into one-level-deep asset files and clearly signaled; not a 5 because the body references docs/release-flow.md, which does not exist in the bundle, and references use backtick paths rather than navigable markdown links.	4 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states both the capability and concrete trigger conditions, tightly scoped to a Changesets-driven monorepo. Minor room to broaden trigger synonyms and enumerate capabilities more fully.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — "Create a PR to the main branch", "identify the affected package(s)", "make sure a changeset exists" — with only minor coverage gaps; not a 5 because the actions are procedural rather than a fully enumerated capability list.	4 / 5
Completeness	Explicitly answers both what ("Create a PR to the main branch ... identify the affected package(s) and make sure a changeset exists") and when ("Use when the user says PRを作成, mainにPR, or wants to submit changes for review") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural trigger coverage including "PRを作成", "mainにPR", and "submit changes for review"; not a 5 because a few common synonyms (e.g. "open a pull request", "submit a PR") are absent.	4 / 5
Distinctiveness Conflict Risk	Clear niche — a pnpm + Changesets monorepo PR workflow with Japanese triggers — that is unlikely to fire for unrelated skills; the "wants to submit changes for review" phrase is slightly broad but the Changesets framing keeps conflict risk minimal.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: breaking-brake/cc-wf-studio
Path: .claude/skills/pr-to-main/SKILL.md
Commit: a7bf24a

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.