What problem does it solve?
Adjusting Markuplint configuration requires knowing which config property fits the intent—rules, excludeFiles, overrides, nodeRules, or childNodeRules—and choosing the wrong scope causes unexpected lint behavior across editors and CI. This Skill analyzes current violations, determines the correct scope, and proposes verified configuration changes.
Core Features & Use Cases
- Violation Analysis: Runs markuplint with JSON output on target files to identify current rule violations before changing anything.
- Scope-Appropriate Configuration: Distinguishes project-wide rules, file-level excludeFiles/overrides, and element-level nodeRules/childNodeRules with CSS selectors.
- Verified Changes: Proposes the exact config edit, confirms with the user, applies it to .markuplintrc, and re-runs lint to report before/after violation counts.
- Use Case: A developer sees a no-unknown-attr warning on meta tags using the OGP property attribute. The Skill proposes a nodeRules block targeting meta[property] that allows the attribute, then verifies the warning disappears.
Quick Start
Ask the assistant to disable the markuplint warning on a specific file or element and let it propose the configuration change.