Individual skill
fec-refactoring-validation
Use when proving that a frontend refactoring preserved existing behavior, selecting an appropriate safety net, validating each structural step, or assigning a PASS, PARTIAL, or NOT PROVEN preservation verdict.
skills/fec-refactoring-validation/SKILL.md
Source commit 5d44782572025045a552ff8945b354726eb5d183
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 23
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- claude-code-plugin Repository topic
- claude-code-skills Repository topic
- e2e-tests Repository topic
- fronend-development Repository topic
- frontend-plugin Repository topic
- frontend-project Repository topic
- react Repository topic
- typescript Repository topic
- vue3 Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,975 bytesreferences/behavior-preservation.mddoc · 1,853 bytesreferences/refactoring-test-checklist.mddoc · 1,820 bytes
Read excerpt
# Skill: Refactoring Validation
## Purpose
Define the observable contract and the smallest credible evidence needed to prove that structural edits preserved existing frontend behavior.
## Procedure
1. Record the relevant behavior contract before substantial edits.
2. Classify safety-net coverage as A, B, or C.
3. Run and record the pre-change baseline.
4. Match verification to the current refactoring risk and affected boundary.
5. After every structural step, run the narrowest sufficient check immediately.
6. If a newly introduced failure appears, revert that step before broader repair.