git-pr

Pull Request creator skill with automated template, testing checklist, security audit checklist, and release notes generator.

Quality

78%

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/git-pr/SKILL.md

Quality

Content

86%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 highly actionable with copy-paste-ready commands and a complete template, organized into a clear four-step workflow with prerequisite validation. Main weakness is the absence of a post-creation validation/error-recovery feedback loop in the publishing step.

Suggestions

Add an explicit validation checkpoint after PR creation (e.g., verify the PR opened, run `gh pr view`, and instructions for what to do if tests fail on CI) to reach the level 5 workflow anchor.

Consider moving the full PR template into a referenced file (e.g. templates/pr_template.md) and keeping only a summary inline, to further tighten conciseness and signal progressive disclosure.

Add a brief error-recovery note for the prerequisite step (what to do when `dotnet test` or `dotnet build` fails) to close the feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is efficient and free of over-explanation of known concepts, but the lengthy inline PR template with emoji decoration and an enumerated microservices list adds bulk that could be trimmed, placing it just below the lean level 5 anchor.	4 / 5
Actionability	Provides fully copy-paste-ready executable commands (git status, git log, dotnet test, dotnet build, gh pr create) and a complete concrete PR template covering the common cases, matching the level 5 anchor.	5 / 5
Workflow Clarity	The four-step sequence (branch analysis, prerequisite validation, title/body generation, PR creation) has clear checkpoints with explicit test/build validation before publishing, but lacks a post-creation feedback loop or error-recovery checkpoint, fitting level 4 rather than 5.	4 / 5
Progressive Disclosure	No bundle files are needed for this self-contained single-purpose skill; the body is well-organized into clear sections (template, release-notes rules, workflow), qualifying for the simple-skill exception that allows a level 5 with well-organized sections.	5 / 5
	Total	18 / 20 Passed

Description

71%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 lists concrete capabilities, but it omits any explicit trigger guidance, which caps completeness at 3. Adding a "Use when..." clause with natural synonyms (e.g., PR, GitHub, merge request) would raise both completeness and trigger_term_quality.

Suggestions

Add an explicit trigger clause such as "Use when creating or preparing Pull Requests, generating release notes, or running testing/security audits before merging."

Include natural synonyms users say, e.g. "PR", "GitHub", "merge request", "code review", so trigger_term_quality reaches comprehensive coverage.

Tighten the phrase to third-person action voice (e.g. "Creates Pull Requests with...") to reinforce distinctiveness and specificity.

Dimension	Reasoning	Score
Specificity	Names the domain and four concrete capabilities ("automated template", "testing checklist", "security audit checklist", "release notes generator"), giving comprehensive coverage of specific actions. Not below 4 since multiple concrete actions are listed, and there is no higher anchor than 5.	5 / 5
Completeness	The description clearly states what the skill does but provides no "Use when..." clause or equivalent explicit trigger guidance; per the rubric guideline, a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Contains several relevant natural terms ("Pull Request creator", "template", "testing checklist", "release notes generator") but lacks common synonyms such as "PR", "GitHub", "merge request" or file extensions, so it falls below the comprehensive level 5 anchor.	4 / 5
Distinctiveness Conflict Risk	"Pull Request creator" with finance-specific security/compliance checklists is a mostly distinct niche, with only minor overlap risk against generic git/PR skills, fitting the level 4 anchor rather than 5.	4 / 5
	Total	16 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: JoseMD12/finance-hub
Path: .agents/skills/git-pr/SKILL.md
Commit: a8dbf2a

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.