markuplint-configure

Configures Markuplint rules at project, file, or element scope based on lint violations.

611|63|Updated Sep 26, 2017
One-click install
npx skills add https://github.com/markuplint/markuplint --skill markuplint-configure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: markuplint-configure
Source: https://github.com/markuplint/markuplint/tree/main/skills/markuplint-configure
Command: npx skills add https://github.com/markuplint/markuplint --skill markuplint-configure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires markuplint.

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.

Frequently Asked Questions about markuplint-configure

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

FAQPage Schema
How do I disable a markuplint rule for specific files?

Use excludeFiles to make markuplint completely ignore the files, or overrides with overrideMode set to merge to keep linting with different rules. excludeFiles also hides warnings in the VS Code extension, while overrides keeps remaining warnings visible.

How to apply a markuplint rule only to certain elements?

Use nodeRules with a CSS selector to target the element itself, or childNodeRules to target its children. Add inheritance set to true in childNodeRules to affect all descendants rather than only direct children.

What is the difference between excludeFiles and overrides in markuplint?

excludeFiles makes markuplint skip the file entirely, including in the VS Code extension. Overrides with merge mode still lints the file but applies different rule settings, so remaining warnings still appear in the editor.

How do I allow custom data attributes in markuplint?

Set the no-unknown-attr rule options with allowAttrs listing your attribute names, such as data-testid. For OGP meta tags, target meta[property] with nodeRules and allow the property attribute across the relevant attribute rules.

Does markuplint configuration affect the VS Code extension?

Yes, excludeFiles and overrides in .markuplintrc both affect VS Code extension behavior. However, glob patterns in npm scripts only affect CLI and CI runs, so VS Code will still lint those files.