agentleFS
vlad-ryzhkovvlad-ryzhkov/ai-context-engineering-for-frontend/.claude/skills/fix-markdown/SKILL.md

fix-markdown

Skill2 starsChanged 8 months agoUnlicenseView on GitHub

Fix all markdownlint errors in .md files across the repository. Use when markdown linting fails in CI or before committing documentation changes. Do not use for content changes — only formatting fixes.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Only fix formatting issues

    line 17
  2. Distinctive:

    Do not change content meaning

    line 18
  3. Distinctive:

    Do not add tables or restructure sections

    line 19
  4. Distinctive:

    Do not rewrite or rephrase text

    line 20
  5. Distinctive:

    Verify: re-run step 2, expect zero errors

    line 37
  6. Distinctive:

    Do NOT output intermediate markdownlint output to chat.

    line 41
  7. Very specific:

    Gardener Protocol: Call .claude/protocols/gardener.md before SKILL COMPLETE.

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fix Markdown Lint Skill

Fix all markdownlint errors in .md files across the repository.

Rules

  • Only fix formatting issues
  • Do not change content meaning
  • Do not add tables or restructure sections
  • Do not rewrite or rephrase text

Steps

  1. Auto-fix what's possible:

    npx markdownlint-cli --fix "**/*.md" --ignore node_modules --ignore ".gradle" --ignore build --ignore audit
  2. Re-run to find remaining issues:

    npx markdownlint-cli "**/*.md" --ignore node_modules --ignore ".gradle" --ignore build --ignore audit
  3. Fix remaining errors manually using Edit tool (line length, heading levels, inline HTML)
  4. Verify: re-run step 2, expect zero errors

Verbosity Protocol (SILENT MODE)

  • Do NOT output intermediate markdownlint output to chat.
  • Output to chat ONLY: blocker messages and the final SKILL COMPLETE block.

Quality Gate

  • npx markdownlint-cli "**/*.md" returns zero errors
  • No content meaning changed
  • No tables added or sections restructured

Gardener Protocol: Call .claude/protocols/gardener.md before SKILL COMPLETE.

Completion Contract

✅ SKILL COMPLETE: /fix-markdown
├─ Files fixed: [N]
├─ Errors resolved: [N]
└─ Remaining: [0 | N with description]

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.