CtrlK
BlogDocsLog inGet started
Tessl Logo

pull-request

Guide for creating proper pull requests for the Biome project. Use when opening a PR, writing a PR description, choosing the correct target branch, or filling out the PR template. Trigger when creating PRs, writing PR summaries, or preparing code for review.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-3

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

The body is highly actionable with concrete commands, examples, and a real PR template, and is well-structured with one-level-deep references. It is slightly held back by minor verbosity and a checklist that lacks an explicit validation feedback loop.

Suggestions

Trim explanatory asides such as 'The summary serves the reviewer' and the rationale paragraphs to keep the body lean.

Reframe the Pre-PR Checklist as a validate→fix→retry workflow (e.g. run 'cargo test' and 'just l', fix any failures, re-run before opening) so validation checkpoints are explicit.

Move the verbose summary/test-plan writing guidance into a short bulleted form to reduce prose tokens.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence, but some prose (e.g. 'The summary serves the reviewer', the rationale for AI disclosure) adds explanatory context that could be tightened.

2 / 3

Actionability

Provides concrete executable commands ('cargo check', 'just f', 'just gen-rules'), real conventional-commit examples, and an exact copy-paste PR template, all ready to use.

3 / 3

Workflow Clarity

The numbered Pre-PR Checklist gives a clear sequence, but checkpoints are implicit and no explicit validate→fix→retry feedback loop is framed, so the sequence stops short of a full validation workflow.

2 / 3

Progressive Disclosure

A single well-organized self-contained file with clear sections and a References block pointing one level deep to real locations (CONTRIBUTING.md, the PR template, external URLs); no bundle files are needed.

3 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 concise, concrete, and answers both what the skill does and when to use it, with explicit trigger guidance and a clear Biome-specific niche. It matches the strongest rubric anchors across all dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'creating proper pull requests', 'writing a PR description', 'choosing the correct target branch', 'filling out the PR template' — rather than vague language.

3 / 3

Completeness

Explicitly answers both 'what' (guide for creating proper PRs for Biome) and 'when' via the 'Use when...' clause plus an additional 'Trigger when...' clause.

3 / 3

Trigger Term Quality

Uses natural phrasing a user would actually say ('opening a PR', 'writing a PR description', 'PR summaries', 'preparing code for review') with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Scoped to 'the Biome project' with domain-specific triggers (target branch selection, PR template) that give it a clear niche unlikely to collide with other skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
biomejs/biome
Reviewed

Table of Contents

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.