branch-wrapup

Pre-PR quality gate that runs build, type-check, lint, test, security scans, and finishes with a conventional commit. Use before creating a PR, after completing features, or when wrapping up a branch.

Quality

83%

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

Quality

Content

77%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 is highly actionable and exceptionally clear in its sequencing and gating, with strong validation checkpoints for a destructive/batch workflow. The main weaknesses are moderate verbosity from repeated patterns and limited progressive disclosure, since the referenced verify.ps1 is not present in the bundle.

Suggestions

Move the large ASCII verification-report template and repeated Select-String snippets into a bundled reference file (e.g. references/report-template.md) and summarize inline.

Include verify.ps1 under scripts/ so the referenced automation is actually part of the skill bundle rather than an external path.

Trim redundant 'What it catches' lists where they restate obvious consequences of the commands above them.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands per phase, but it repeats similar Select-String patterns across phases, restates gate rules in prose after tables, and includes some boilerplate ('What it catches') that Claude already knows.	3 / 5
Actionability	Every phase supplies copy-paste-ready PowerShell commands with specific paths and patterns, plus a fully worked verification-report template and a bundled verify.ps1 with documented flags.	5 / 5
Workflow Clarity	Ten phases are explicitly sequenced, each with blocking/soft/info gate status summarized in a gate-rules table, explicit stop conditions (build fail, HIGH OWASP, P0 smell), and troubleshooting/feedback loops for recovery.	5 / 5
Progressive Disclosure	No references/ or assets/ bundle exists; verify.ps1 is referenced but lives outside this bundle, and the OWASP detail is delegated to another skill — structure is reasonable but the inlined Select-String blocks and report template could be split out.	3 / 5
	Total	16 / 20 Passed

Description

88%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 strong: it states concrete capabilities, gives explicit 'Use when...' trigger guidance, and occupies a distinct pre-PR quality-gate niche. Its only weakness is slightly limited keyword variation for trigger terms.

Suggestions

Add a few natural synonyms or shorthand triggers (e.g. 'pre-PR check', 'verify before pushing') to broaden keyword coverage.

Optionally name the primary stack context (e.g. 'for React/TypeScript + Azure projects') to sharpen distinctiveness versus generic CI skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'runs build, type-check, lint, test, security scans, and finishes with a conventional commit' — giving comprehensive coverage of the skill's behavior.	5 / 5
Completeness	Explicitly answers both what (the verification and commit workflow) and when ('Use before creating a PR, after completing features, or when wrapping up a branch') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('before creating a PR', 'after completing features', 'wrapping up a branch') but lacks synonyms/file extensions and could be marginally broader.	4 / 5
Distinctiveness Conflict Risk	The 'pre-PR quality gate' framing carves a clear niche distinct from general code-review or commit skills, with only minor overlap risk against a generic git-commit skill.	4 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: 0xrabbidfly/eric-cartman
Path: .github/skills/branch-wrapup/SKILL.md
Commit: 0b8453f

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