菜单
Ensures markdown files conform to rumdl linting rules and personal formatting preferences. Use when creating or editing .md files, or when user mentions formatting, linting, or rumdl.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Reference for writing and editing skills well - the vocabulary and principles that make a skill predictable.
Implement a piece of work based on a PRD or set of issues.
Ensures issue titles conform with a specific style. Use when creating or editing an issue.
Ensures PR (Pull Request) titles conform with a specific style. Use when creating or editing a PR.
| description | Ensures markdown files conform to rumdl linting rules and personal formatting preferences. Use when creating or editing .md files, or when user mentions formatting, linting, or rumdl. |
| name | conform-markdown |
Ensure markdown files comply with rumdl linting rules and personal preferences.
These override rumdl defaults where they conflict:
**text** or __text__).—, replace it with hyphen -.—, replace it with hyphen -.., except standalone terms or bare links.- This is the first line of the list item.
This is the second line of the list item.
- Another list item.
1. This is the first line.
This is the second line.
This is the Third line.
2. Another list item.
When creating or editing a markdown file:
.rumdl.toml under exclude.
If so, skip linting entirely.rumdl fmt --config 'MD013.reflow=true' <file> to auto-format.rumdl check --fix <file> to auto-fix linting warnings.rumdl check <file> again to verify no warnings remain.exclude in .rumdl.toml.Respect .rumdl.toml at the repo root if present.
It may configure enabled/disabled rules, exclusions, and rule-level settings.
GitHub's Markdown renderer diverges from CommonMark on line breaks: consecutive lines without a blank line between them are rendered as separate lines (unlike standard Markdown where they are joined). Therefore, do NOT hard-wrap long lines in issue/PR descriptions or comments. Let each paragraph stay a single long line.
// Standard CommonMark: renders as one joined line
This is the first line.
This is the second line.
// GitHub: renders as two separate lines
This is the first line.
This is the second line.