fm-clean-code

Audits generated React migration code for quality, accessibility, and convention compliance.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/ohmyhotelco/hare-cc-plugins --skill fm-clean-code-ohmyhotelco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fm-clean-code
Source: https://github.com/ohmyhotelco/hare-cc-plugins/tree/main/frontend-migration-plugin/skills/fm-clean-code
Command: npx skills add https://github.com/ohmyhotelco/hare-cc-plugins --skill fm-clean-code-ohmyhotelco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing large volumes of generated React migration code by hand is slow and inconsistent, making it easy for naming issues, weak typing, accessibility gaps, and over-engineering to slip into the codebase. ## Core Features & Use Cases - Standalone Quality Audit: Runs a quality-reviewer agent on any path, fully independent of the migration pipeline with no progress tracking or lock requirements. - Multi-Dimension Review: Scores composition, naming, types, accessibility, performance, convention compliance, and simplicity/over-engineering with file:line references. - App-Aware Configuration: Resolves the target app (pc, mobile, or hana) and its directories from the plugin config, with localized reports in the configured working language. - Use Case: After migrating a legacy page to React, run the audit on the generated source directory to get an overall score plus the top issues ranked by severity before merging. ## Quick Start Ask the assistant to run a clean code audit on the generated React code for the current app, optionally passing a specific path or an app flag such as --app mobile.

Frequently Asked Questions about fm-clean-code

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

FAQPage Schema
How do I review generated React code for quality issues?▼

Run the clean code audit on the target directory containing the generated React code. It launches a quality-reviewer agent that scores composition, naming, types, accessibility, performance, and simplicity, then reports findings with file:line references and suggested fixes.

How to audit React migration code without running the full pipeline?▼

This audit is completely independent of the migration pipeline. It requires no progress tracking, lock, or feature context, so you can point it at any path and get a standalone quality report without affecting pipeline state.

Can I run the code audit on a specific app like mobile or hana?▼

Yes, pass the --app flag with pc, mobile, or hana. The app entry must exist in the plugin configuration with resolved appDir and targetDir; an unconfigured app stops with a clear error before the review starts.

What happens if the plugin config file is missing?▼

The audit reads .claude/frontend-migration-plugin.json at startup. If the file is absent, it instructs you to run fm-init first and stops, since app directories and working language cannot be resolved without it.

Does the code audit modify my source files or pipeline state?▼

No, the audit is read-only. The reviewer agent only reads code and writes a report; it never changes source files, mutates pipeline state, or takes the pipeline lock.