CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gitnexus-refactoring

Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable content: every tool call is concrete with expected output, and the refactor checklists bake in dry-run/verify/test feedback loops for safety. Minor trimming of the duplicated rename example would tighten it further.

DimensionReasoningScore

Conciseness

The body is lean and tool-focused with no over-explanation of concepts Claude already knows, but the Example section largely repeats the rename flow already shown in Tools/Checklists, and "Run tests for affected processes" appears three times.

4 / 5

Actionability

Fully executable guidance: concrete tool calls with parameters and realistic outputs (rename with dry_run, impact, detect_changes), a real Cypher query, and a terminal command for the stale-index case.

5 / 5

Workflow Clarity

Clear sequence ("interfaces → implementations → callers → tests") and checklists with explicit validation checkpoints — dry_run preview, review edits, detect_changes verification, and test runs — forming feedback loops around the batch edit operation.

5 / 5

Progressive Disclosure

Well-organized single file with clear sections and no buried content, but at ~120 lines with everything inlined (including a full worked example and Cypher samples) it exceeds the simple-skill profile and could split detail into reference files.

4 / 5

Total

18

/

20

Passed

Description

91%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 description: it names the refactoring niche with concrete action verbs and pairs them with highly natural example trigger phrases users would actually say. The only weaknesses are the vague qualifier "safely" and the absence of what mechanism the skill contributes.

DimensionReasoningScore

Specificity

Lists several concrete actions ("rename, extract, split, move, or restructure code") with minor gaps — "safely" is vague and the description never states what the skill actually provides (graph-based impact analysis and automated multi-file rename).

4 / 5

Completeness

Explicitly answers both: the what is the action list ("rename, extract, split, move, or restructure code safely") and the when is a clear "Use when the user wants to..." clause with concrete example triggers.

5 / 5

Trigger Term Quality

Comprehensive natural user phrases with synonyms: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file" — exactly what a user would say when they need this skill.

5 / 5

Distinctiveness Conflict Risk

Refactoring is a mostly distinct niche with clear triggers, but the broad phrase "restructure code" carries minor overlap risk with general code-editing skills.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

tslateman/shipyard

Path

.claude/skills/gitnexus/gitnexus-refactoring/SKILL.md

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.