CtrlK
BlogDocsLog inGet started
Tessl Logo

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"

65

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/gitnexus-refactoring/SKILL.md
SKILL.md
Quality
Evals
Security

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 tight, actionable refactoring skill body with concrete tool calls, risk mitigations, and validation-gated checklists. Its main weakness is mild redundancy between the Tools reference and the closing worked example.

Suggestions

Trim or cross-reference the closing worked example so it does not restate the rename/impact/detect_changes calls already shown in the Tools section.

Consider moving the per-tool parameter details into a reference file and keeping SKILL.md as an overview, which would let progressive disclosure reach the top anchor.

DimensionReasoningScore

Conciseness

Lean, code-block-driven content that assumes Claude knows refactoring concepts; the closing worked example partially re-traces the Tools section, a minor bit of padding that could be trimmed.

4 / 5

Actionability

Provides concrete tool invocations with parameters and sample outputs (rename, impact, detect_changes, cypher) covering the common cases; mostly executable with only minor gaps around tool availability/entrypoints.

4 / 5

Workflow Clarity

Checklists sequence dry_run preview, review, apply, detect_changes, and test runs with explicit validation checkpoints and feedback loops for these destructive batch refactors, matching the top anchor.

5 / 5

Progressive Disclosure

Well-organized into clear sections (When to Use, Workflow, Checklists, Tools, Risk Rules, Example) with no nested references and no bundle files; the self-contained Tools and Example sections overlap slightly, a minor organization gap.

4 / 5

Total

17

/

20

Passed

Description

75%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 well-constructed description with concrete actions, natural trigger phrases, and an explicit 'Use when' clause. Both what and when are present, though the capability is framed inside the trigger rather than declared separately.

Suggestions

Lead with a brief declarative capability statement (e.g., 'Safely renames, extracts, splits, and moves code across a codebase.') before the 'Use when' clause to make the 'what' fully explicit.

Add a few more refactoring verbs or synonyms (inline, change signature, pull up) to round out trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete refactoring actions ("rename, extract, split, move, or restructure code") but misses common variations like inline, change signature, or pull-up, placing it just below comprehensive.

4 / 5

Completeness

Has both a what (the verb list) and an explicit when ("Use when..." plus four concrete example triggers); the capability is embedded in the trigger clause rather than stated as a standalone declarative, keeping it just below the top anchor.

4 / 5

Trigger Term Quality

Provides natural user utterances ("Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file") with good coverage, though a few synonymous phrasings are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear refactoring niche with distinct triggers; minor overlap risk only with closely related general code-editing skills.

4 / 5

Total

16

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
abhigyanpatwari/GitNexus
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.