refactorer

Code refactoring expert - clean code, patterns, restructuring

Quality

37%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/refactorer/SKILL.md

Quality

Content

52%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill provides excellent concrete code examples demonstrating refactoring patterns, making it highly actionable. However, it lacks workflow guidance on how to approach refactoring tasks (identify smells → plan changes → refactor → validate), and explains SOLID principles that Claude already knows well. The content would benefit from being more concise and adding a clear refactoring process with validation steps.

Suggestions

Add a workflow section with steps: 1) Identify code smells, 2) Choose appropriate pattern, 3) Apply refactoring, 4) Run tests to validate, 5) Review for further improvements

Remove or significantly condense the SOLID principles explanations - Claude knows these; instead, just reference them as decision criteria

Add validation checkpoints like 'Run tests after each refactoring step' and 'Verify behavior unchanged before proceeding'

Consider splitting detailed pattern examples into a separate PATTERNS.md file, keeping SKILL.md as a concise overview with the refactoring workflow

Dimension	Reasoning	Score
Conciseness	The examples are clear and well-structured, but the content is quite lengthy with extensive before/after code blocks. Some patterns (like SOLID principles) could be condensed since Claude already understands these concepts.	2 / 3
Actionability	Provides fully executable TypeScript code examples with clear before/after comparisons. Each refactoring pattern shows concrete, copy-paste ready transformations that Claude can directly apply.	3 / 3
Workflow Clarity	No workflow or process is defined for how to approach refactoring. Missing guidance on when to apply which pattern, how to validate refactoring didn't break functionality, or any sequence of steps for a refactoring session.	1 / 3
Progressive Disclosure	Content is organized into logical sections (Refactoring Patterns, SOLID Principles, Code Smells), but everything is in one monolithic file. No references to external files for detailed pattern catalogs or advanced techniques.	2 / 3
	Total	8 / 12 Passed

Description

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too terse and vague to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and sufficient detail to distinguish it from other code-related skills. The description reads more like a category label than actionable guidance for Claude.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks to improve code quality, reduce complexity, eliminate code smells, or apply design patterns'

List specific refactoring actions such as 'extract methods, rename variables, reduce cyclomatic complexity, apply SOLID principles, eliminate duplication'

Include natural trigger terms users would say: 'messy code', 'spaghetti code', 'technical debt', 'code smell', 'simplify this function'

Dimension	Reasoning	Score
Specificity	The description uses vague terms like 'clean code', 'patterns', and 'restructuring' without specifying concrete actions. It doesn't list what specific refactoring operations are performed (e.g., extract method, rename variables, reduce complexity).	1 / 3
Completeness	The description only vaguely addresses 'what' (refactoring expert) and completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('refactoring', 'clean code', 'patterns', 'restructuring') that users might say, but misses common variations like 'improve code', 'code smell', 'technical debt', 'simplify', or 'optimize code structure'.	2 / 3
Distinctiveness Conflict Risk	While 'refactoring' provides some specificity, terms like 'clean code' and 'patterns' are broad enough to potentially overlap with general coding skills, code review skills, or design pattern skills.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: TurnaboutHero/oh-my-antigravity
Commit: fab464f

Reviewed: 4 months 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.