pr

Rules and checklist for preparing PRs, creating changesets, and releasing packages in the monorepo.

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/pr/SKILL.md

Quality

Content

72%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.

The content is lean and actionable with clean section structure and an appropriate one-level cross-reference, but the PR-prep workflow lacks explicit validation checkpoints and feedback loops. Sequencing the commands with pass/fail gates would strengthen workflow clarity.

Suggestions

Turn the command list into an ordered workflow with explicit pass/fail gates, e.g. "Run format/lint/typecheck/tests; only proceed to `pnpm changeset` when all pass."

Add concrete changeset guidance (e.g. which bump type to select, expected CHANGELOG.md effect) instead of only listing `pnpm changeset`.

Remove the redundant intro sentence since the "What It Does" bullets already convey the same information.

Dimension	Reasoning	Score
Conciseness	The body is lean with short bullets and executable commands and assumes Claude's competence; the only redundancy is the intro restating the "What It Does" bullets, fitting score 4 rather than the fully-trimmed 5.	4 / 5
Actionability	Concrete executable commands (pnpm format, lint:fix, typecheck, test, changeset) and a checkbox checklist are provided, but "What It Does" describes changeset usage without specifics on filling one out, leaving minor gaps versus the copy-paste-ready 5.	4 / 5
Workflow Clarity	A logical command sequence and a checklist gate exist, but validation checkpoints are implicit and there is no explicit "only proceed when X passes" feedback loop, matching the sequence-present-but-checkpoints-implicit anchor 3.	3 / 5
Progressive Disclosure	This is a simple under-50-line skill with well-organized sections (When to Use, What It Does, Commands, Checklist, Related Skills) and a single clearly-signaled one-level cross-reference to the changelog skill, qualifying for the simple-skill exception at 5.	5 / 5
	Total	16 / 20 Passed

Description

66%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.

The description is specific and uses natural trigger terms within a clear monorepo niche, but it omits any explicit "when to use" guidance, which caps its completeness. Adding a "Use when..." clause would raise the strongest weakness.

Suggestions

Add an explicit trigger clause such as "Use when preparing a PR, adding a changeset, or releasing packages in the monorepo" to satisfy the completeness "when" requirement.

Include common synonyms users say (e.g. "pull requests", "version bump", "changelog") to broaden trigger-term coverage toward 5.

Clarify the monorepo-specific scope (e.g. pnpm workspaces / changesets) to further reduce overlap with a generic changelog skill.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "preparing PRs, creating changesets, and releasing packages" — within a named domain, matching the "several specific actions; minor gaps" anchor rather than the 1-2 actions of score 3.	4 / 5
Completeness	It states clearly what the skill covers ("Rules and checklist for preparing PRs, creating changesets, and releasing packages") but provides no "Use when..." clause or explicit trigger guidance, so completeness is capped at 3 per the missing-when guideline.	3 / 5
Trigger Term Quality	Natural terms a user would say ("PRs", "changesets", "releasing packages", "monorepo") are present, but common variations like "pull requests", "version bump", or "changelog" are missing, fitting score 4 over comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	The monorepo PR/changeset/release niche is mostly distinct, with only minor overlap risk against the closely related changelog skill, matching score 4 rather than the fully-niche 5.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: kubb-labs/kubb
Path: .agents/skills/pr/SKILL.md
Commit: 1bbf973

Reviewed: about 18 hours 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.