finishing-a-development-branch

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Quality

76%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/finishing-a-development-branch/SKILL.md

Quality

Discovery

75%

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 effectively communicates a clear niche use case with explicit 'when' triggers, making it strong on completeness and distinctiveness. However, it could benefit from more specific concrete actions beyond 'presenting structured options' and broader trigger term coverage to capture natural user language variations.

Suggestions

Add more specific concrete actions, e.g., 'creates pull request descriptions, suggests branch cleanup steps, recommends merge strategies'

Expand trigger terms to include natural variations like 'pull request', 'ready to merge', 'finished coding', 'done implementing', 'ready to ship'

Dimension	Reasoning	Score
Specificity	The description names some actions ('merge, PR, or cleanup') and describes the domain ('completion of development work'), but the actions are not comprehensively listed - it's more about presenting options than performing concrete actions.	2 / 3
Completeness	Clearly answers both what ('guides completion of development work by presenting structured options for merge, PR, or cleanup') and when ('when implementation is complete, all tests pass, and you need to decide how to integrate the work') with explicit trigger conditions.	3 / 3
Trigger Term Quality	Includes some relevant terms like 'merge', 'PR', 'tests pass', and 'cleanup' that users might naturally use, but misses common variations like 'pull request', 'push', 'branch', 'done coding', 'finished implementation', or 'ready to ship'.	2 / 3
Distinctiveness Conflict Risk	This has a clear niche - it's specifically about the post-implementation decision point for integrating completed work. It's unlikely to conflict with coding skills, testing skills, or git skills because it targets a very specific workflow stage.	3 / 3
	Total	10 / 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 well-structured, highly actionable skill with clear workflow sequencing and proper validation checkpoints. Its main weakness is moderate verbosity—the 'Common Mistakes' and 'Red Flags' sections largely restate constraints already embedded in the workflow steps, consuming tokens without adding much new information. Overall it's a solid skill that Claude could follow precisely.

Suggestions

Consolidate 'Common Mistakes' and 'Red Flags' into a single brief 'Constraints' section to reduce redundancy with the workflow steps.

Consider trimming the 'Common Mistakes' entries to single-line reminders rather than Problem/Fix pairs, since the fixes are already encoded in the workflow.

Dimension	Reasoning	Score
Conciseness	Generally efficient but includes some unnecessary sections like 'Common Mistakes' and 'Red Flags' that largely repeat what's already stated in the workflow steps. The quick reference table is a nice touch but the content could be tightened by removing redundant guidance.	2 / 3
Actionability	Provides fully executable bash commands for every option, specific git commands, gh CLI usage for PR creation, and concrete test commands. The exact text to present to users is specified, making this highly copy-paste ready.	3 / 3
Workflow Clarity	Clear 5-step sequence with explicit validation checkpoints: tests must pass before proceeding, tests re-run after merge, typed confirmation required before discard. Includes proper feedback loops (stop if tests fail) and clear branching logic for each option.	3 / 3
Progressive Disclosure	Well-organized with clear sections and a useful quick reference table, but the content is somewhat long for a single file with no bundle files. The 'Common Mistakes' and 'Red Flags' sections could potentially be separated or consolidated, though the Integration section nicely signals relationships to other skills.	2 / 3
	Total	10 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: lucianghinda/superpowers-ruby
Commit: 7500b1f

Reviewed: about 13 hours 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.