CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-finalize

Finalizes any PR for merge by verifying title/description match implementation AND performing code review for best practices. Use when asked to "finalize PR", "check PR description", "review commit message", before merging any PR, or when PR implementation changed during review. Do NOT use for extracting lessons (use learn-from-pr), writing tests (use write-tests-agent), or investigating build failures (use azdo-build-investigator and ci-analysis).

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The content is actionable, clearly sequenced with validation checkpoints, and well-structured with appropriate progressive disclosure. Its main weakness is verbosity from duplicated guardrail sections and full template blocks that could be condensed.

Suggestions

Deduplicate the 'Do NOT Post Comments Directly' / analysis-only warning — keep one canonical version and reference it instead of repeating it verbatim across two sections.

Condense or relocate the full markdown output templates and 'Quality Comparison Examples' into the references bundle to reduce token load while preserving the actionable commands and guardrails inline.

Tighten the Phase 2 'How to Review' section by merging the repeated critical-rules table with the Phase 1 rules table rather than restating them.

DimensionReasoningScore

Conciseness

The body is mostly efficient but repeats the 'Do NOT Post Comments Directly' warning and analysis-only message verbatim (twice) and carries long full-template examples that pad the token budget; it could be tightened.

2 / 3

Actionability

Provides concrete executable gh commands, a specific title formula, copy-ready markdown output templates, and a table of required elements — fully actionable guidance.

3 / 3

Workflow Clarity

A clearly sequenced two-phase workflow (title/description review then code review) with numbered evaluation steps, template-comparison validation, and hard NEVER guardrails acting as checkpoints.

3 / 3

Progressive Disclosure

SKILL.md serves as a well-organized overview with a single one-level-deep, clearly signaled reference to references/complete-example.md (verified to exist), keeping the full worked example out of the main body.

3 / 3

Total

11

/

12

Passed

Description

100%

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, trigger-rich, complete, and highly distinct from sibling skills, with both positive triggers and explicit do-not-use routing. It is a strong, model-quality skill description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'verifying title/description match implementation' and 'performing code review for best practices' — matching the top anchor rather than the partial-coverage score 2.

3 / 3

Completeness

Explicitly answers both what (verify title/description + code review) and when via a clear 'Use when...' clause with multiple triggers, satisfying the top anchor.

3 / 3

Trigger Term Quality

Includes natural phrases users would actually say ('finalize PR', 'check PR description', 'review commit message', 'before merging any PR') with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

A 'Do NOT use for...' clause explicitly routes away from learn-from-pr, write-tests-agent, azdo-build-investigator, and ci-analysis, giving it a clear niche with low conflict risk.

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
dotnet/maui
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.