frontend-refactor-worker

Name: frontend-refactor-worker
Availability: InStock
Author: qredence

Coordinate frontend file moves, import updates, and symbol renames with validation.

51|6|Updated Feb 7, 2026

Search Tags:#automation #frontend #build #refactor #imports #symbols #type-check

Ready to run

npx skills add https://github.com/Qredence/fleet-rlm --skill frontend-refactor-worker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: frontend-refactor-worker
Source: https://github.com/Qredence/fleet-rlm/tree/main/.factory/skills/frontend-refactor-worker
Command: npx skills add https://github.com/Qredence/fleet-rlm --skill frontend-refactor-worker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill centralizes complex frontend refactor work by coordinating file moves, import path updates, and symbol renames across a codebase, while ensuring all changes are validated by type-check, lint, unit tests, and build steps.

Core Features & Use Cases

Move frontend files between directories and update imports and symbols consistently.
Update targeted configuration files (vite.config.ts, AGENTS.md) as part of a feature refactor.
Validate changes through sequential checks: type-check, lint, unit tests, and build, with safeguards to prevent broken deployments.

Quick Start

Install and invoke the frontend-refactor-worker workflow to perform a guided refactor following the procedure described above.

Frequently Asked Questions about frontend-refactor-worker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate frontend file moves and import updates across a large codebase?▼

Automating frontend file moves requires coordinating directory changes with consistent import path updates and symbol renames across modules. This workflow propagates changes to configuration files like vite.config.ts and AGENTS.md to maintain codebase integrity during refactoring.

What's the best way to validate frontend refactors before deployment?▼

Validating frontend refactors involves running sequential checks for type-check, lint, unit tests, and build steps. This process enforces safety safeguards against broken deployments by verifying that file moves, import updates, and symbol renames pass end-to-end validation.

Can I rename symbols and preserve dual-name exports during a frontend refactor?▼

Renaming symbols during frontend refactoring can preserve dual-name exports by applying consistent propagation rules across modules. This workflow handles symbol renames while maintaining backward compatibility for existing import statements throughout the codebase.

Does this frontend refactor workflow update configuration files like vite.config.ts?▼

Updating configuration files like vite.config.ts and AGENTS.md is supported as part of a feature refactor. The workflow applies targeted config file updates alongside file moves, import path changes, and symbol renames to ensure all references remain consistent.

How do I handle frontend refactoring for large codebases with many interconnected modules?▼

Large frontend codebases require consistent propagation of changes across interconnected modules and configuration files. This workflow centralizes coordinated refactor tasks—moving files, updating imports, and renaming symbols—while running comprehensive validation to catch cross-module breakages.

What type of validation checks run after updating imports and moving frontend files?▼

Validation checks for import updates and file moves include sequential type-check, lint, unit tests, and build verification. These end-to-end safeguards prevent broken deployments by ensuring all coordinated refactor changes pass before integration.