Conciseness

Lean and largely code/checklist driven with no padding explaining what refactoring is; assumes Claude's competence. A touch of repetition between the Tools and Example sections keeps it just at 3 rather than slipping to 2.

Actionability

Provides concrete, executable tool calls such as rename({symbol_name: "validateUser", new_name: "authenticateUser", dry_run: true}) with realistic outputs and a worked end-to-end example — copy-paste ready rather than pseudocode.

Workflow Clarity

Sequenced workflow (impact → query → context → plan) plus checklists with explicit validation checkpoints (dry_run preview, review ast_search edits, detect_changes, run tests) for destructive batch renames, matching the level-3 anchor.

Progressive Disclosure

Self-contained single-file skill with no bundle files and no need for external references; content is organized into clear sections (When to Use, Workflow, Checklists, Tools, Risk Rules, Example) enabling easy navigation.

Specificity

Lists multiple concrete actions — "rename, extract, split, move, or restructure code" — matching the level-3 anchor of several specific concrete actions rather than naming only a domain and a couple actions.

Completeness

Explicitly answers both what (rename/extract/split/move/restructure code safely) and when ("Use when the user wants to...") with an explicit trigger clause, meeting the level-3 anchor and avoiding the cap at 2 for a missing Use-when clause.

Trigger Term Quality

Natural phrasings users would actually say ("Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file") give good coverage; not below 3 because no common variation is missing, and not vague jargon.

Distinctiveness Conflict Risk

Carves a clear niche (code refactoring via GitNexus) with distinct triggers unlikely to fire for unrelated skills; not 2 because it is not merely a domain label but a specific operation set.