new-branch-and-pr

Create a fresh branch, complete work, and open a pull request

Quality

31%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./cursor-team-kit/skills/new-branch-and-pr/SKILL.md

Quality

Discovery

32%

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 captures a high-level git workflow (branch → work → PR) but is too terse and lacks critical details. 'Complete work' is vague filler, there are no explicit trigger terms or a 'Use when...' clause, and common keyword variations like 'PR', 'git', or 'merge request' are missing.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to start a new feature, fix a bug on a branch, or open a pull request for review.'

Replace the vague 'complete work' with specific actions like 'implement code changes, commit updates' to clarify what the skill actually does.

Include common keyword variations such as 'PR', 'git branch', 'merge request', 'feature branch', and 'code review' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names three actions (create branch, complete work, open PR) but 'complete work' is vague and the description lacks detail about what kind of work or how it's done.	2 / 3
Completeness	Describes what it does (create branch, do work, open PR) but has no 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also weak due to 'complete work' being vague, bringing it to 1.	1 / 3
Trigger Term Quality	Includes natural terms like 'branch', 'pull request' that users would say, but misses common variations like 'PR', 'git', 'merge request', 'feature branch', or 'code review'.	2 / 3
Distinctiveness Conflict Risk	The combination of branch creation and PR opening is somewhat specific to a git workflow skill, but 'complete work' is generic enough to overlap with many development-related skills.	2 / 3
	Total	7 / 12 Passed

Implementation

29%

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

This skill provides a high-level outline of a branch-and-PR workflow but lacks the concrete, executable guidance that would make it useful. The steps read more like a checklist of intentions than actionable instructions—there are no git or gh CLI commands, no examples of branch naming conventions, no PR template, and no validation steps. The structure is clean but the content is too abstract to meaningfully guide Claude.

Suggestions

Add concrete, executable commands for each workflow step (e.g., `git checkout main && git pull && git checkout -b feat/description`, `gh pr create --title '...' --body '...'`).

Include a specific example showing branch naming convention, a sample commit message, and a sample PR body template.

Add validation checkpoints such as verifying tests pass before pushing (`make test` or equivalent) and checking the PR was created successfully.

Provide a concrete example of the expected output (branch name format, PR summary format, PR URL) rather than just listing output categories.

Dimension	Reasoning	Score
Conciseness	The content is relatively brief and doesn't over-explain concepts Claude knows, but it's also quite thin—mostly generic descriptions without much substance. The guardrails and output sections are lean but the workflow steps are vague filler rather than earning their tokens.	2 / 3
Actionability	No concrete commands, code, or executable examples are provided. Steps like 'Create a descriptive branch from the latest main' and 'Complete implementation and tests' are vague directions rather than actionable instructions—no git commands, no gh CLI examples, no PR template.	1 / 3
Workflow Clarity	While steps are listed in sequence, they lack any concrete commands (e.g., `git checkout -b`, `git push`, `gh pr create`), have no validation checkpoints, and 'Complete implementation and tests' is an unbounded step that provides no guidance. There are no feedback loops or error recovery steps.	1 / 3
Progressive Disclosure	For a simple, single-purpose skill under 50 lines with no bundle files, the content is organized into clear sections (Trigger, Workflow, Guardrails, Output) that are easy to scan. No external references are needed for this scope.	3 / 3
	Total	7 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: cursor/plugins
Commit: b8f2564

Reviewed: 3 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.