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

1.92x

Quality

82%

Does it follow best practices?

Impact

98%

1.92x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

The canonical home for this skill is finishing-a-development-branch in obra/superpowers

Quality

Content

81%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.

A highly actionable, well-sequenced workflow with strong validation checkpoints for destructive operations. Main weaknesses are mild redundancy across the Common Mistakes and Red Flags sections and a few placeholder/generic command gaps.

Suggestions

Collapse the 'Red Flags / Always' list into 'Common Mistakes' (or vice versa) to remove restated guidance like 'Verify tests before offering options' and 'Present exactly 4 options'.

Replace the '<test command>' placeholder in the merge option with a concrete re-run instruction (e.g. 're-run the same test command from Step 1') so the loop is fully copy-paste ready.

Condense the generic 'npm test / cargo test / pytest / go test ./...' line to an instruction like 'run the project's standard test command' to avoid implying a specific stack.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands and minimal concept explanation, but the 'Common Mistakes' and 'Red Flags / Always' sections restate process steps (e.g. 'Verify tests before offering options' appears repeatedly) and could be trimmed; not a 5 due to this redundancy.	4 / 5
Actionability	Provides concrete, executable git/gh commands with a full PR heredoc template covering the common cases; not a 5 because of placeholders like '<test command>' and the generic 'npm test / cargo test / pytest / go test ./...' listing that leave a minor gap.	4 / 5
Workflow Clarity	Clear 5-step sequence with explicit validation checkpoints (verify tests before options with a hard stop, re-verify tests on merged result, typed 'discard' confirmation for the destructive option) and stop conditions, satisfying the destructive-operation validation requirement.	5 / 5
Progressive Disclosure	Well-organized into clear sections (Overview, Process, Quick Reference, Common Mistakes, Red Flags, Integration) with no nested references; not a 5 because at ~200 lines with no bundle files, some inline content (mistakes/red-flags) could be condensed or externalized.	4 / 5
	Total	17 / 20 Passed

Description

83%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.

A strong, well-structured description that clearly states both purpose and trigger conditions with concrete, natural language. Minor room to improve keyword breadth and reduce slightly abstract framing around 'presenting structured options'.

Suggestions

Add common synonyms users might say, e.g. 'finish branch', 'ship the work', or 'close out a feature branch', to broaden trigger coverage.

Tighten the 'what' clause to lead with concrete actions ('merge, create a PR, keep, or discard a completed development branch') rather than the abstract 'guides completion... by presenting structured options'.

Dimension	Reasoning	Score
Specificity	Names several concrete actions ('merge, PR, or cleanup') for the development-branch-completion domain, with only minor coverage gaps; not a 5 because 'guides completion... by presenting structured options' is mildly abstract framing rather than a comprehensive action list.	4 / 5
Completeness	Explicitly answers both 'what' ('guides completion of development work by presenting structured options for merge, PR, or cleanup') and 'when' with concrete trigger phrases ('Use when implementation is complete, all tests pass, and you need to decide how to integrate the work').	5 / 5
Trigger Term Quality	Includes natural developer phrases ('implementation is complete', 'all tests pass', 'merge', 'PR', 'cleanup', 'integrate the work') that users would plausibly say; not a 5 because it lacks common synonyms/variations (e.g. 'finish branch', 'ship', 'close branch').	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (post-implementation branch finishing) with distinct combined triggers (tests pass + need to decide integration); not a 5 because it has minor overlap risk with general git/PR or merge skills.	4 / 5
	Total	17 / 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: roman01la/skills-agents
Path: skills/finishing-a-development-branch/SKILL.md
Commit: aa6f9d3

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