refactor-pass

Perform a refactor pass focused on simplicity after recent changes. Use when the user asks for a refactor/cleanup pass, simplification, or dead-code removal and expects build/tests to verify behavior.

1.00x

Quality

81%

Does it follow best practices?

Impact

97%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

78%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, well-structured instruction-only skill with an efficient workflow and a validation step. Its main weakness is actionability: several refactor directives are abstract rather than concrete, and the verification step lacks an explicit failure-recovery loop.

Suggestions

Make the refactor directives more concrete, e.g. 'Remove dead code: delete functions/variables with no callers (check via grep or compiler warnings)' instead of just 'Remove dead code'.

Add a feedback loop after 'Run build/tests to verify behavior', e.g. 'If tests fail, revert or fix the offending refactor and re-run before suggesting abstractions.'

Briefly specify how to detect simplification opportunities (e.g. 'review the diff for duplicated logic, unused parameters, and convoluted conditionals') so the first step is actionable rather than abstract.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or explanation of concepts Claude already knows; every line earns its place, matching the top anchor for an instruction-only skill.	5 / 5
Actionability	Some steps are concrete ('Remove dead code', 'Run build/tests') but others are abstract direction ('Straighten logic flows', 'Remove premature optimization') with no method for identifying them; matches the 'some concrete guidance but incomplete' anchor rather than the mostly-executable 4.	3 / 5
Workflow Clarity	Clear four-step sequence with a validation checkpoint ('Run build/tests to verify behavior'); not a 5 because there is no explicit error-recovery feedback loop (what to do when tests fail), leaving a minor validation gap for a code-modifying skill.	4 / 5
Progressive Disclosure	A simple skill under 50 lines with no need for external references, organized under a clear 'Workflow' section, qualifying for the top anchor per the simple-skills scoring note.	5 / 5
	Total	17 / 20 Passed

Description

83%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 concise, well-constructed description that clearly states both capability and explicit trigger conditions with natural user phrasing. It is distinct enough for its niche with only minor overlap risk against general code-editing skills.

Dimension	Reasoning	Score
Specificity	Names several concrete refactor actions ('simplification', 'dead-code removal', 'cleanup pass', 'build/tests to verify behavior'), matching the 'lists several specific actions; minor gaps' anchor; not a 5 because 'focused on simplicity' is still somewhat abstract rather than a fully enumerated action set.	4 / 5
Completeness	Explicitly answers both 'what' ('Perform a refactor pass focused on simplicity after recent changes') and 'when' with a concrete 'Use when...' clause listing trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	Includes natural terms a user would say — 'refactor', 'cleanup pass', 'simplification', 'dead-code removal' — giving good keyword coverage with synonyms; not a 5 because there are no file-extension or further synonym variants, though that is partly inherent to a code skill.	4 / 5
Distinctiveness Conflict Risk	The 'refactor pass focused on simplicity after recent changes' framing carves a reasonably distinct niche; not a 5 because refactor/cleanup/simplify language overlaps with general code-editing skills.	4 / 5
	Total	17 / 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: pgplex/pgconsole
Path: .claude/skills/refactor-pass/SKILL.md
Commit: bf166f0

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