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"

77

Quality

96%

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

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

Excellent body: concise, fully actionable, with strong validation feedback loops for destructive refactors and clear section structure. Nothing significant to improve.

DimensionReasoningScore

Conciseness

Lean and efficient; assumes Claude's competence, explains only non-obvious traps (binding identity, partial/truncated flags, wrong-worktree zero), every token earns its place.

5 / 5

Actionability

Fully executable tool calls with arguments and return shapes, per-operation checklists, and a worked end-to-end rename example; copy-paste ready.

5 / 5

Workflow Clarity

Destructive/batch operation with explicit dry_run preview gate, identity confirmation, detect_changes verification, and a partial/truncated re-run feedback loop, plus checklists for each refactor type.

5 / 5

Progressive Disclosure

No bundle files present; the ~160-line body is well-organized with clear section headers and no nested references, fitting the simple-skill exception for a 5.

5 / 5

Total

20

/

20

Passed

Description

92%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, third-person description with explicit trigger guidance and concrete example phrases. Only minor room to add a few more natural synonyms like "inline".

DimensionReasoningScore

Specificity

Lists five concrete restructuring actions (rename, extract, split, move, restructure) with comprehensive coverage, matching the score-5 anchor.

5 / 5

Completeness

Explicitly answers both what (rename/extract/split/move/restructure code safely) and when (Use when + Examples) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Four natural quoted example phrases ("Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file") plus verbs give good coverage, but a few common synonyms/variations are absent.

4 / 5

Distinctiveness Conflict Risk

Clear refactoring niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

19

/

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.