rumdl — Markdown Linting and Formatting

Use rumdl to keep Markdown consistent with fast linting, safe auto-fixes, markdownlint-compatible rules, CI output formats, and project-local configuration.

Workflow

1. Inspect existing Markdown config first: .rumdl.toml, rumdl.toml, .markdownlint*, CI config, prek hooks, and just recipes.
2. Preserve the project's style choices. Do not enable stricter prose wrapping or HTML restrictions unless the user asks.
3. Use rumdl import when migrating from markdownlint, then make .rumdl.toml the source of truth.
4. Run rumdl check first for audits and verification. Run rumdl check --fix only when the user wants automatic cleanup; run rumdl check again for final verification.
5. Report changed config, files auto-fixed, and any remaining manual issues.

Critical Rules for Agents

1. Use rumdl check for verification. It reports violations and exits non-zero when problems remain.
2. Do not auto-fix unless requested. Use rumdl check for audits and verification; use rumdl check --fix only when the user asks for cleanup or approves modifying Markdown files.
3. Do not use rumdl fmt as the only CI gate. Formatter mode applies fixes and exits successfully; pair it with check for enforcement.
4. Keep configuration local and explicit. Prefer .rumdl.toml in the repository root so agents and CI share the same rules.
5. Use CI-native output when available. Prefer --output-format github on GitHub Actions and --output-format gitlab on GitLab when running rumdl directly.