CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pr-merge-champion

Optimize pull requests for quick approval and merging by ensuring clean diffs, comprehensive self-reviews, and structured documentation.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/pr-merge-champion/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 body delivers a clear, well-sequenced PR preparation playbook with genuinely executable git commands and a strong worked example. Its weaknesses are modest verbosity — Best Practices and Common Pitfalls restate widely known engineering norms — and high-level verification steps that lack specific commands or feedback loops.

Suggestions

Trim the Best Practices and Common Pitfalls sections to only non-obvious, project-specific guidance, cutting widely known advice like "Do Not Ignore CI Failures" and "rebase to avoid merge conflicts".

Make Step 3 concrete with example commands (e.g., "npm test && npm run lint" or a language-agnostic fallback) and add an explicit feedback loop: if tests or linters fail, fix and re-run before proceeding.

Consider moving the full example PR description template into a referenced file and keeping only a compact skeleton inline to reduce token load.

DimensionReasoningScore

Conciseness

The four core steps are reasonably tight, but the "Best Practices" section ("Do Not Ignore CI Failures", "Keep PRs Small and Focused") and "Common Pitfalls" restate engineering knowledge Claude already has, fitting "mostly efficient but includes some unnecessary explanation or could be tightened". Not level 4 because several sentences across those sections could be cut entirely without losing guidance.

3 / 5

Actionability

Provides executable commands ("git status --porcelain", "git diff | grep -E '(console\.log|debugger|print\(|var_dump|binding\.pry)'") and a complete example PR description. Not level 5 because several steps remain high-level — "Run local linters, formatters, and compilers" and "Run the project's automated test suite" give no specific commands or fallbacks.

4 / 5

Workflow Clarity

A clear four-step sequence (rebase → self-review → verify → describe) with most checkpoints present (linters/compilers, test suite, manual edge-case testing). Not level 5 because there are no explicit feedback loops (e.g., "if tests fail, fix and re-run") and Step 2's self-review has no verification that issues found were actually resolved.

4 / 5

Progressive Disclosure

With no bundle files, the single SKILL.md is well organized under clear headers (When to Use, How It Works, Examples, Best Practices, Limitations, Common Pitfalls). Not level 5 because at ~105 lines it exceeds the simple-skill threshold, and the two examples and pitfalls sections are content that could be split into referenced files; not level 3 since structure and placement are already good.

4 / 5

Total

15

/

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 communicates a concrete, well-scoped capability set around pull-request preparation and merges efficiently without padding. Its main weakness is the absence of any "Use when..." trigger guidance, which both caps completeness and omits natural trigger phrases (PR, code review, GitHub) that would improve discoverability and distinctiveness.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g., "Use when preparing to open a pull request, self-reviewing a branch, or when the user mentions PRs, code review, or merge approval."

Include common natural variations and synonyms such as "PR", "code review", and "GitHub" to broaden trigger-term coverage.

Make the capability list slightly more concrete (e.g., "rebases branches, removes debug leftovers, runs test suites, and writes structured PR descriptions") to reach fully specific coverage.

DimensionReasoningScore

Specificity

"ensuring clean diffs, comprehensive self-reviews, and structured documentation" lists several specific actions in the pull-request domain, matching the level-4 anchor. It falls short of level 5 because the actions are outcome-level rather than a comprehensive inventory of concrete capabilities (e.g., rebase, lint, test, write the description).

4 / 5

Completeness

The "what" is clear (optimize PRs via clean diffs, self-reviews, structured documentation), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not level 2 because the "what" half is concrete and specific.

3 / 5

Trigger Term Quality

Natural terms like "pull requests", "approval", "merging", "diffs", and "self-reviews" give good keyword coverage, but common variations users say — "PR", "code review", "GitHub" — are missing. This matches level 4 ("a few natural terms missing") rather than level 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The PR-approval/merge focus carves a clear niche that is mostly distinct, with only minor overlap risk against closely related PR-writing or code-review skills. Not level 5 because it lacks distinct trigger phrases that would fully separate it from those neighbors.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/pr-merge-champion/SKILL.md

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.