fec-refactoring-validationUse 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.
Install via ClawdBot CLI:
clawdbot install bovinphang/fec-refactoring-validationGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/bovinphang/frontend-craftAudited Sep 30, 2026 · audit v1.0
Generated Sep 29, 2026
A fintech dashboard team needs to migrate a core transaction table component from Vue 2 Options API to Vue 3 Composition API without changing its behavior for downstream consumers. They use this skill to record prop/emit contracts, run a pre-change baseline, and validate each structural step with the narrowest sufficient check. The final verdict determines whether the migration can ship or needs more characterization tests.
A design system team extracts shared UI components from a monolithic React app into a standalone package without altering DOM structure, accessibility semantics, or event ordering. They apply this skill to classify safety-net coverage, add characterization tests for under-covered behavior, and enforce GREEN → REFACTOR → GREEN after every extraction step. The PASS/PARTIAL/NOT PROVEN verdict gates the package release.
An ecommerce agency refactors Liquid templates and JavaScript bundles for a high-traffic Shopify store to improve Core Web Vitals, while preserving checkout flows, cart state, and analytics events. The skill guides them to preserve the behavioral contract around DOM structure, network payloads, and request ordering, then run broad gates before the freeze. A NOT PROVEN verdict blocks deployment until gaps are closed.
A healthcare portal team converts a large Angular module to standalone components to reduce bundle size, needing proof that routing guards, reactive form logic, and lifecycle timing remain unchanged. They use this skill to establish an A/B/C safety-net level, run per-step checks, and capture unresolved coverage gaps. The verdict is attached to the release checklist for compliance review.
A media streaming company rewrites its Redux store into Zustand slices, risking changes to cache keys, memoization, and loading/error transitions. This skill helps engineers record the behavioral contract, add characterization tests for partial coverage, and revert any step that introduces new failures. The resulting preservation record supports a defensible PASS decision before rollout.
A consultancy offers fixed-scope frontend refactoring validation engagements where experts apply the skill to produce behavior-preservation records, safety-net classification, and PASS/PARTIAL/NOT PROVEN verdicts. Clients receive audit-ready evidence that structural changes did not alter user-facing behavior, reducing release risk. This positions validation as a standalone productized service rather than billable hours.
A SaaS product integrates with GitHub Actions and GitLab CI to enforce refactoring validation rules: requiring baseline records, classifying safety-net levels, and blocking merges lacking a PASS verdict. Teams configure thresholds and let the plugin generate the expected behavior-preservation record automatically. This turns the skill into a recurring compliance layer for engineering organizations.
Independent agent builders sell or license this skill as a composable module inside AI coding assistants and autonomous refactoring agents. Buyers pay for a validated skill pack that improves agent reliability during structural edits by enforcing evidence-based verdicts. The marketplace takes a platform fee while creators earn per download, seat, or successful validation run.
💬 Integration Tip
Embed this skill as a required gate in CI/CD so every structural step records its behavior contract, safety-net level, and narrowest sufficient check before merge. Pair it with an agent framework that can load the referenced markdown files to auto-generate the behavior-preservation record.
Scored Sep 30, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.