@markuplint/ml-core-maintenance

Maintain the @markuplint/ml-core linting engine with TypeScript builds and rule mappings.

606|64|Updated Sep 26, 2017
One-click install
npx skills add https://github.com/markuplint/markuplint --skill markuplint-ml-core-maintenance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: @markuplint/ml-core-maintenance
Source: https://github.com/markuplint/markuplint/tree/main/packages/%40markuplint/ml-core
Command: npx skills add https://github.com/markuplint/markuplint --skill markuplint-ml-core-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured guide to maintain the core ml-core linting engine, covering architecture awareness, task templates, and safe update practices.

Core Features & Use Cases

  • Maintenance guidance for adding MLDOM properties, mapping rules, and pretender updates.
  • Procedural tasks for implementing new rules, adjusting rule mappings, and updating test utilities.
  • Use Case: A maintainer updates the MLDocument creation flow to support new node types and ensures builds succeed across downstream packages.

Quick Start

Follow the detailed maintenance steps to implement changes and verify builds in your environment.

Frequently Asked Questions about @markuplint/ml-core-maintenance

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

FAQPage Schema
How do I add new node properties to the markuplint MLDOM without breaking existing rules?

Adding MLDOM properties requires updating the MLDocument creation flow and adjusting rule mappings. The maintenance process ensures TypeScript builds succeed and backward compatibility is preserved through RuleMapper and violation reporting.

What is the process for updating pretenders in the markuplint core engine?

Updating pretenders in the markuplint core engine involves modifying related tooling within the ml-core architecture. Maintainers follow procedural maintenance tasks to apply pretender updates and verify that downstream packages build successfully with TypeScript.

How do I implement a new linting rule and map it correctly in markuplint?

Implementing a new linting rule requires using procedural task templates to define the rule and adjust its mappings. Maintainers must align rule config resolution and create corresponding test utilities to validate the MLRule and violation reporting.

Does markuplint core maintenance support TypeScript build verification for downstream packages?

Yes, markuplint core maintenance explicitly ensures that architectural changes and updates across MLDocument and MLDOM build successfully with TypeScript. This verification step aligns rule config resolution and maintains compatibility across downstream packages.

When should I update the RuleMapper and MLRule configurations during linting engine maintenance?

Update RuleMapper and MLRule configurations when adding MLDOM properties or modifying rule mappings. This ensures that rule config resolution stays aligned and backward compatibility is maintained through accurate violation reporting across the linting engine.