CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

migration-refactor-specialist

Planeja e executa migracoes e refatoracoes incrementais. Trigger em: "migracao de framework", "modernizacao de legacy", "strangler pattern", "refactor estrutural", "upgrade grande", "extracao incremental", "migracao de runtime", "trocar ORM", "rollout incremental de refactor", "migrar para", "spring boot 3", "spring boot 2 para 3", "jakarta migration", "javax para jakarta", "openrewrite", "upgrade spring boot", "migrar jdk 21", "jdk 21 upgrade", "java 21 migration", "spring boot upgrade", "spring 3 migration".

Quality

80%

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 ./skills/23-migration-refactor-specialist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 lean, well-sectioned orchestration skill with a genuinely strong per-phase validation-and-rollback loop and thoughtful safety carve-outs (the delete-list immutable-constraint rule). Its main weaknesses are that executable detail is deferred to playbook/template files that do not exist in this bundle, and the promised outputs are described abstractly without a concrete example of a phase plan.

Suggestions

Ship the referenced bundle files (playbooks/spring-boot-2-to-3.md, playbooks/references/*.md, templates/migration-plan.md, policies/*.md) or inline the essential content — every deferred reference currently points to a file absent from the bundle.

Add a minimal worked example of one migration phase (objective, temporary compatibility strategy, validation criteria, rollback trigger) so the 'plano incremental' output is concrete rather than an artifact name.

Sequence the end-to-end workflow (assessment → plan → phase loop → handoff → review) as a numbered list, and merge the redundant delete-list categories 1 and 5 ('Código morto' vs 'Branches inalcançáveis').

DimensionReasoningScore

Conciseness

The body is efficient — short sectioned lists ('Quando Usar', 'Checklist Base', a compact playbook table) with no explanations of concepts Claude already knows, matching 'efficient; minor instances that could be trimmed'. It is not 5 because of redundancy: delete-list items 1 ('Código morto — branches/funções inalcançáveis') and 5 ('Branches inalcançáveis — condição sempre falsa/verdadeira, dead code após return/throw') overlap substantially, and the governance file enumeration could be tightened.

4 / 5

Actionability

There is some concrete guidance (the per-phase checkpoint 'rodar a suite de testes completa... executar o rollback documentado', and the delete-list evidence rule 'citar arquivo:linha... grep/symbol search sem match'), but the core migration execution guidance stays at the artifact level ('estrategia de compatibilidade temporaria explicita', 'rollback e criterio de corte documentados') with the actual steps deferred to playbook/template files that are not present in the bundle — matching 'some concrete guidance but incomplete'. It is not 4 because a reader of this file alone lacks the specific steps to produce the promised incremental plan.

3 / 5

Workflow Clarity

The central phase loop is explicit with validation and a feedback path: 'aplicar a fase → rodar a suite de testes completa → se falhar, corrigir ou executar o rollback documentado... Só avançar quando a suite estiver verde', plus a base checklist — matching 'clear sequence with most checkpoints present'. It is not 5 because the end-to-end workflow (assess current state → build plan → phase loop → handoff → review) is never sequenced; only the per-phase loop is, and the validation applies to test suites rather than to plan artifacts.

4 / 5

Progressive Disclosure

In-body structure is good and references are clearly signaled (a playbook table with 'Quando usar' and one-line descriptions of `playbooks/references/common-fixes.md` and `custom-parent-strategy.md`), but every deferred target — `playbooks/`, `playbooks/references/`, `templates/migration-plan.md`, `policies/*.md`, `GLOBAL.md` — is absent from the actual bundle, so navigation dead-ends at runtime. This lands between 'references present but not clearly signaled' (3) and 'good structure; references mostly clear' (4): the signaling earns 4, the broken/missing bundle targets pull it back to 3.

3 / 5

Total

14

/

20

Passed

Description

86%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 description: third-person, explicit 'what' and 'when', with an unusually comprehensive list of natural trigger terms including version-specific synonyms. The only notable gap is that the capability sentence itself is thin — two generic verbs — leaving the full scope to be inferred from the trigger list.

DimensionReasoningScore

Specificity

The capability statement 'Planeja e executa migracoes e refatoracoes incrementais' names the domain plus two concrete actions (plan, execute), matching the 'names domain and 1-2 concrete actions' anchor. It is not score 4 because the actions listed are generic — no enumeration of what kinds of migrations or artifacts are produced beyond the generic 'plan/execute'.

3 / 5

Completeness

It explicitly answers both 'what' ('Planeja e executa migracoes e refatoracoes incrementais') and 'when' ('Trigger em: ...' with concrete trigger phrases), matching the top anchor. It is not score 4 because the 'when' clause is not merely present — it enumerates explicit concrete trigger phrases rather than leaving timing implicit.

5 / 5

Trigger Term Quality

The trigger list is comprehensive with natural synonyms and version-specific phrasing users would actually say: 'migracao de framework', 'modernizacao de legacy', 'strangler pattern', 'trocar ORM', 'migrar para', 'spring boot 2 para 3', 'javax para jakarta', 'openrewrite', 'jdk 21 upgrade', 'java 21 migration'. This matches the 'comprehensive coverage of natural terms including synonyms' anchor; it is not below because both casual and technical variants are present.

5 / 5

Distinctiveness Conflict Risk

The niche (large incremental migrations/refactors, strangler pattern, Spring Boot 2→3) is mostly distinct with specific triggers, matching 'mostly distinct; minor overlap risk'. It is not 5 because 'migrar para' and 'trocar ORM' are broad enough to also fire for data/storage or ORM-specific skills in a dense skill ecosystem.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

felvieira/claude-skills-fv

Path

skills/23-migration-refactor-specialist/SKILL.md

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.