sync-stale-branches

Brings diverged remote branches up to date with develop — classifies, rescues unique work, then resets or deletes stale branches

Quality

76%

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 ./.claude/skills/sync-stale-branches/SKILL.md

Quality

Content

82%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 a lean, highly actionable multi-step git workflow with a real verification checkpoint, earning top marks for conciseness. Minor gaps — an undefined external procedure reference in Step 5b and the absence of an explicit failure-handling feedback loop on the verify step — keep actionability and workflow_clarity just below full marks.

Suggestions

Replace the reference to the undefined 'feature-branch-extraction procedure' with inline commands or a concrete pointer so Claude can execute Step 5b without external knowledge.

Add an explicit feedback loop after Step 6: if any branch shows non-zero ahead/behind, return to the relevant step and re-verify rather than proceeding.

Make the Step 5a module-to-feature mapping rule more concrete (e.g. a naming convention or a fallback command) so file grouping is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's git competence: every section is a short purpose statement plus executable commands, with no padding or restating of git concepts Claude already knows.	5 / 5
Actionability	Most steps are concrete, executable git commands, but Step 5a's 'group uncovered files by module/domain' and the reference to an undefined 'feature-branch-extraction procedure' leave minor gaps in execution detail.	4 / 5
Workflow Clarity	The six-step sequence is clear with a dedicated Verify step (ahead/behind checks) and an expected-result assertion, but a destructive/batch workflow would benefit from an explicit 'stop if verification fails' feedback loop.	4 / 5
Progressive Disclosure	The content is well organized into clearly labeled sections at one level with no nested references, and is appropriately compact for a self-contained skill; no bundle files exist, so structure is judged on the body alone.	4 / 5
	Total	17 / 20 Passed

Description

58%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 concretely conveys a multi-phase workflow but lacks an explicit 'Use when...' trigger clause, capping completeness, and its trigger terms are domain-technical rather than the natural phrasings users say. It is mostly distinct from other skills.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g. 'Use when the remote branch list is cluttered with stale/diverged branches, or when asked to clean up or sync old branches').

Include user-natural synonyms and phrasings like 'clean up branches', 'sync old branches', or 'prune stale branches' alongside the technical terms.

Optionally mention the broader trigger of periodic branch cleanup so Claude reaches for it proactively.

Dimension	Reasoning	Score
Specificity	The description names several concrete actions ('classifies', 'rescues unique work', 'resets', 'deletes stale branches'), giving clear coverage of the workflow phases, but stops short of listing every discrete action.	4 / 5
Completeness	The 'what' is clearly stated via a sequence of concrete actions, but there is no explicit 'Use when...' trigger clause, so 'when' is only weakly implied.	3 / 5
Trigger Term Quality	It uses domain terms like 'diverged remote branches', 'develop', and 'stale branches', but omits natural phrasings a user might say ('clean up branches', 'sync branches', 'prune old branches') and lacks synonyms.	3 / 5
Distinctiveness Conflict Risk	The niche is fairly specific (diverged remote branches relative to develop) and is unlikely to trigger for unrelated skills, with only minor overlap risk with general git housekeeping.	4 / 5
	Total	14 / 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: Bottelet/DaybydayCRM
Path: .claude/skills/sync-stale-branches/SKILL.md
Commit: 2199c1e

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