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.
Install with Tessl CLI
npx tessl i github:0xrabbidfly/eric-cartman --skill branch-wrapup87
Quality
81%
Does it follow best practices?
Impact
100%
1.51xAverage score across 3 eval scenarios
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly communicates both capabilities and usage triggers. It lists specific actions (build, type-check, lint, test, security scans, conventional commit) and provides explicit 'Use when' guidance. The main weakness is trigger term coverage could include more natural variations like 'pull request' or 'ready to merge'.
Suggestions
Add common trigger term variations like 'pull request', 'ready to merge', 'code review prep', or 'check my code' to improve discoverability
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'runs build, type-check, lint, test, security scans, and finishes with a conventional commit'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('runs build, type-check, lint, test, security scans, conventional commit') and when ('before creating a PR, after completing features, or when wrapping up a branch') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some natural terms like 'PR', 'features', 'branch', but missing common variations users might say like 'pull request', 'merge', 'code review', 'ready to merge', or 'check my code'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche as a 'pre-PR quality gate' with distinct triggers around PR creation and branch completion. The combination of quality checks plus conventional commit makes it unlikely to conflict with individual linting or testing skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent workflow clarity and executable commands throughout. The main weakness is verbosity - the skill could be more concise by trimming explanatory text about what each phase catches (Claude knows what type errors are) and potentially splitting detailed phase content into separate reference files.
Suggestions
Remove 'What it catches' explanations under each phase - Claude understands what build failures and type errors are
Consider moving detailed phase commands to a separate PHASES.md reference file, keeping SKILL.md as a concise overview with the gate rules table and quick start
Trim the 'When to Use' section - these scenarios are self-evident from the skill's purpose
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., explaining what each phase catches when Claude would understand from the commands). The phase descriptions could be tighter, and some sections like 'When to Use' list obvious scenarios. | 2 / 3 |
Actionability | Excellent executable guidance with copy-paste ready PowerShell commands for every phase. Specific patterns to search for, exact commands to run, and clear output format expectations make this highly actionable. | 3 / 3 |
Workflow Clarity | Clear 9-phase sequence with explicit gate rules table showing which phases block progression. Includes validation checkpoints (P0 smells stop immediately, constitutional violations block PR) and feedback loops for error recovery. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is quite long (~300 lines) with detailed inline content that could be split. References to verify.ps1 and other skills are present but the main content is monolithic rather than layered. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.