code-fix

Fixes convention-audit report deviations with diff previews and mandatory re-validation.

5|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ChenyCHENYU/wl-skills-kit --skill code-fix-chenychenyu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-fix
Source: https://github.com/ChenyCHENYU/wl-skills-kit/tree/main/files/.wl-skills/skills/ops/code-fix
Command: npx skills add https://github.com/ChenyCHENYU/wl-skills-kit --skill code-fix-chenychenyu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running a convention audit, teams face dozens of low-to-medium severity code convention deviations (missing scoped styles, missing cid attributes, import order issues) that are tedious to fix by hand but risky to change blindly in bulk. This Skill applies controlled, user-confirmed fixes to those reported issues without touching business logic. ## Core Features & Use Cases - Controlled issue fixing: Reads the convention-audit report, resolves each issue's file, line, and deviation type, then applies rule-based or AI-based patches only after a diff preview is confirmed. - Severity gating: Fixes only medium and low severity deviations; critical structural issues are refused and routed to page regeneration or manual work. - Mandatory re-validation: After each fix round it automatically re-runs page validation and reports remaining errors, closing the loop before commit. - Use Case: Before a pull request, run the audit, then ask to fix all rule-based deviations in the report; review each diff group, confirm, and get a re-scan summary showing zero remaining errors. ## Quick Start Ask the AI to fix all medium and low severity issues listed in reports/规范审查报告.md with diff previews before each change.

Frequently Asked Questions about code-fix

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

FAQPage Schema
How do I fix convention audit report issues automatically?

Run the convention audit first to generate the report, then request fixes by issue ID, group, or severity level. Each fix shows a diff preview that you must confirm before any file is written, and a re-validation scan runs afterward.

What is the difference between code-fix and ESLint --fix?

ESLint --fix handles syntax and formatting rules automatically, while this Skill fixes project-internal conventions that ESLint does not cover, such as cid attributes, scoped style wrappers, and table column definitions. They complement each other; run ESLint first.

Can it fix critical severity deviations automatically?

No. Critical severity deviations involving structural errors or contract mismatches are refused and must be handled manually or by regenerating the page with the page generation skill. Only medium and low severity issues are eligible.

Can I skip the diff confirmation and fix everything at once?

No. Confirmation before writing is a core design constraint and cannot be bypassed. Every file change requires a diff preview and explicit user approval to prevent uncontrolled bulk modifications.

Why does code-fix require a convention audit report first?

The Skill does not scan code itself; it consumes the audit report as its input snapshot, using the listed issue IDs, file paths, and line numbers to locate deviations precisely. Without a current report, fixes could target stale or wrong locations.