.claude/skills/fec-refactoring-validationRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
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.
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/fec-refactoring-validationRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/fec-refactoring-validationRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/fec-refactoring-validationRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @bovinphang/fec-refactoring-validationclawhub inspect @bovinphang/fec-refactoring-validation --version 2.9.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:44ba30ebae291ab4cd3b0c638aabc9182ba9446305408c4fec9d70f4e8ac3d22LICENSEmetadata.jsonpackage.jsonREADME.mdreferences/behavior-preservation.mdreferences/refactoring-test-checklist.mdskill-card.mdSKILL.md- Expanded and clarified documentation for refactoring validation steps and criteria. - Added detailed procedures for recording behavior contracts and assigning preservation verdicts. - Introduced explicit safety-net coverage levels (A, B, C) with execution guidance. - Included a comprehensive checklist for frontend contract elements to guide validation. - Outlined strict constraints to ensure credible behavior-preservation evidence.