Skip to content

Extend Markdown linters comparison page and link from README - #204

Merged
jeduden merged 7 commits into
mainfrom
copilot/add-comparisons-page-markdown-linters
May 1, 2026
Merged

Extend Markdown linters comparison page and link from README#204
jeduden merged 7 commits into
mainfrom
copilot/add-comparisons-page-markdown-linters

Conversation

Copilot AI commented Apr 29, 2026

Copy link
Copy Markdown
Contributor
  • Diagnose why broken plan reference links slipped past mdsmith's lint action (MDS027 walks *ast.Link only; goldmark drops undefined [text][label] to plain text and never visits unreferenced link definitions)
  • Identify why the gap was invisible in docs/background/markdown-linters.md
  • Draft plan/124_no-space-in-code-spans.md (MDS038-equivalent rule)
  • Draft plan/125_no-space-in-link-text.md (MDS039-equivalent rule)
  • Draft plan/126_no-trailing-punctuation-in-headings.md (MDS026-equivalent rule)
  • Draft plan/127_single-h1.md (MDS025-equivalent rule)
  • Draft plan/128_no-undefined-reference-labels.md (MDS052-equivalent rule)
  • Draft plan/129_no-unused-link-definitions.md (MDS053-equivalent rule)
  • Split the "Reference links" comparison row so MD052 / MD053 / forbidding-reference-style are tracked separately, and add link-reference entries for the new plans
  • Extend the comparison page with Hugo, Obsidian, security-posture, and future-plan sections, plus a generated README link sourced from the page's front matter
  • Regenerate PLAN.md catalog so the new plans appear
  • Apply review-thread fixes: drop invalid enabled: keys from rule config snippets in plans 124/125/127/128/129; lowercase the h1 heading conflicts with front-matter title example in plan 127; American normalization spelling
  • mdsmith check clean for the new and modified files (pre-existing MDS026 width warning on PLAN.md is unchanged)

@jeduden

jeduden commented Apr 29, 2026

Copy link
Copy Markdown
Owner

Use front matter and then use to link the doc in readme. This is to ensure the description is colocated with the content.

@jeduden
jeduden marked this pull request as ready for review April 29, 2026 08:55
Copilot AI review requested due to automatic review settings April 29, 2026 08:55
@codecov

codecov Bot commented Apr 29, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.10%. Comparing base (0ef6d47) to head (b9c4d2d).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #204   +/-   ##
=======================================
  Coverage   94.10%   94.10%           
=======================================
  Files         132      132           
  Lines       14725    14725           
=======================================
  Hits        13857    13857           
  Misses        528      528           
  Partials      340      340           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Expands mdsmith’s documentation comparing it to other Markdown tools (including Hugo, query, security posture, and future plans) and makes that comparison easier to discover from the README.

Changes:

  • Added a Hugo entry and a Hugo-vs-mdsmith generated-content comparison table to the linters comparison page.
  • Documented mdsmith query, added a security posture comparison section, and linked relevant plans and references.
  • Added a “How does it compare?” callout in the README linking to the comparison page.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
docs/background/markdown-linters.md Adds Hugo, query, security posture, future plans, and supporting reference links.
README.md Adds a prominent link/callout to the comparison page after “Why mdsmith”.

Comment thread docs/background/markdown-linters.md Outdated
Comment thread docs/background/markdown-linters.md Outdated
Copilot AI requested a review from jeduden April 29, 2026 09:02
Copilot AI review requested due to automatic review settings April 29, 2026 13:21

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Expands the Markdown linters comparison doc to cover additional tools/capabilities (including Hugo, security posture, and future plans) and adds a prominent README link to that comparison so users can quickly evaluate mdsmith against alternatives.

Changes:

  • Added a Hugo comparison subsection, expanded the structural linting matrix, and updated the structural summary narrative.
  • Added new sections covering security posture and future plans, with plan/doc link references.
  • Linked the comparison page from README.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File Description
docs/background/markdown-linters.md Extends and restructures the comparison content; adds Hugo + security posture + future plans; adds new rule/plan link refs.
README.md Adds a “How does it compare?” callout linking to the comparison doc.

Comment thread docs/background/markdown-linters.md
Comment thread docs/background/markdown-linters.md Outdated
Comment thread docs/background/markdown-linters.md Outdated
@jeduden

jeduden commented Apr 29, 2026

Copy link
Copy Markdown
Owner

@copilot apply changes based on the comments in this thread and include obsidian

Copilot AI commented Apr 29, 2026

Copy link
Copy Markdown
Contributor Author

Use front matter and then use to link the doc in readme. This is to ensure the description is colocated with the content.

Done in 2a871e1. The README "How does it compare?" callout now uses a <?catalog?> directive that generates the link text directly from the summary field in the comparison doc's front matter. The summary was also shortened so the generated line stays within the 100-char limit.

@copilot apply changes based on the comments in this thread and include obsidian

Done in 2a871e1. Applied all three review-thread fixes (alias rejection cell, sanitization spelling, artifacts spelling) and added an Obsidian subsection in Tool Overview covering wikilinks/callouts/linting/front matter/agent-friendliness with a comparison table.

Copilot AI requested review from Copilot and removed request for Copilot April 30, 2026 05:21
Copilot AI requested review from Copilot and removed request for Copilot April 30, 2026 06:03
@jeduden
jeduden requested a review from Copilot April 30, 2026 06:11

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Expands the repository’s “Markdown linters comparison” documentation and surfaces it from top-level entry points, while adding new plan documents for upcoming link-reference integrity rules (MD052/MD053 parity).

Changes:

  • Added plans for MDS052 (undefined reference labels) and MDS053 (unused/duplicate link reference definitions), plus additional upcoming rule plans.
  • Expanded docs/background/markdown-linters.md with new tool sections (Hugo, Obsidian), a security posture section, and updated comparison tables.
  • Linked the comparison page from README.md and refreshed generated catalogs in contributor instruction files; regenerated PLAN.md to include the new plans.

Reviewed changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 7 comments.

Show a summary per file
File Description
plan/124_no-space-in-code-spans.md New plan for MDS048 (space in code spans).
plan/125_no-space-in-link-text.md New plan for MDS049 (space in link text).
plan/126_proper-names.md New plan for MDS050 (proper-name capitalization).
plan/127_single-h1.md New plan for MDS051 (single H1).
plan/128_no-undefined-reference-labels.md New plan for MDS052 (undefined reference labels).
plan/129_no-unused-link-definitions.md New plan for MDS053 (unused/duplicate link reference definitions).
docs/background/markdown-linters.md Expanded comparison content; updated summary used by catalogs; added security posture and future plans sections.
README.md Added a catalog-backed link to the comparison page.
PLAN.md Regenerated plan catalog to include new plans.
CLAUDE.md Updated catalog entry text for the comparison page.
AGENTS.md Updated catalog entry text for the comparison page.
.github/copilot-instructions.md Updated catalog entry text for the comparison page.
Comments suppressed due to low confidence (1)

docs/background/markdown-linters.md:174

  • The LLM discussion under “Tool Overview” no longer has a ### LLM as Linter heading (it currently starts with a paragraph after the Obsidian section). Add back an h3 heading so this section remains scannable and consistent with the other tool subsections.
Using language models (GPT-4, Claude, etc.) directly to
check prose quality, conciseness, and style. This is
emerging through dedicated CLI tools and AI review bots.

Comment thread plan/129_no-unused-link-definitions.md Outdated
Comment thread docs/background/markdown-linters.md Outdated
Comment thread plan/124_no-space-in-code-spans.md Outdated
Comment thread plan/125_no-space-in-link-text.md Outdated
Comment thread plan/127_single-h1.md Outdated
Comment thread plan/127_single-h1.md Outdated
Comment thread plan/128_no-undefined-reference-labels.md Outdated
@jeduden

jeduden commented May 1, 2026

Copy link
Copy Markdown
Owner

@copilot apply changes based on the comments in this thread

Copilot AI commented May 1, 2026

Copy link
Copy Markdown
Contributor Author

@copilot apply changes based on the comments in this thread

Applied all seven items from that thread in 9d45f44: removed the invalid enabled: true lines from the config snippets in plans 124, 125, 127, 128, 129; lowercased the h1 heading conflicts with front-matter title example in plan 127; and switched normalisationnormalization in the comparison page.

Copilot finished work on behalf of jeduden May 1, 2026 08:34
Copilot AI and others added 7 commits May 1, 2026 11:07
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
…sues; add Obsidian

Agent-Logs-Url: https://github.com/jeduden/mdsmith/sessions/3991a7bc-82a8-4cb8-bcc2-78a21b8fe49a

Co-authored-by: jeduden <1117699+jeduden@users.noreply.github.com>
…nks, proper-names, single-H1)

Agent-Logs-Url: https://github.com/jeduden/mdsmith/sessions/86a0ecef-882c-4f8e-b485-e94e86adbad1

Co-authored-by: jeduden <1117699+jeduden@users.noreply.github.com>
Copilot AI review requested due to automatic review settings May 1, 2026 09:07
@jeduden
jeduden force-pushed the copilot/add-comparisons-page-markdown-linters branch from 9d45f44 to b9c4d2d Compare May 1, 2026 09:07

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR expands the project’s “Markdown linters comparison” documentation and makes it discoverable from the README, while also adding/including new plan documents that the comparison page links to (notably for proposed MD052/MD053 parity rules).

Changes:

  • Extend docs/background/markdown-linters.md with additional tool comparisons (e.g., Hugo, Obsidian), a security posture section, and updated capability tables/plan links.
  • Add a generated link to the comparison page from README.md.
  • Add new plan documents (124–129) and regenerate PLAN.md so the plan catalog includes them; update generated doc catalogs to use the new comparison-page summary text.

Reviewed changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
plan/124_no-space-in-code-spans.md New plan document referenced from the comparison page’s capability table.
plan/125_no-space-in-link-text.md New plan document referenced from the comparison page’s capability table.
plan/126_proper-names.md New plan document referenced from the comparison page’s capability table.
plan/127_single-h1.md New plan document referenced from the comparison page’s capability table.
plan/128_no-undefined-reference-labels.md New plan for an MD052-equivalent rule, referenced from the comparison page.
plan/129_no-unused-link-definitions.md New plan for an MD053-equivalent rule, referenced from the comparison page.
docs/background/markdown-linters.md Main expansion: new tool sections, updated structural linting table, security posture, and refreshed link references.
README.md Adds a generated catalog/link pointing readers to the comparison page.
PLAN.md Regenerated plan catalog to include plans 124–129.
CLAUDE.md Updates the generated docs catalog entry text for the comparison page.
AGENTS.md Updates the generated docs catalog entry text for the comparison page.
.github/copilot-instructions.md Updates the generated docs catalog entry text for the comparison page.
Comments suppressed due to low confidence (1)

docs/background/markdown-linters.md:176

  • The LLM section lost its heading: after the Obsidian section, the text starting with "Using language models…" is now part of the Obsidian section because there’s no new ### header. Reintroduce a ### LLM as Linter (or similar) heading before this paragraph so the document structure/TOC matches the intent.
Using language models (GPT-4, Claude, etc.) directly to
check prose quality, conciseness, and style. This is
emerging through dedicated CLI tools and AI review bots.

How it works:

Comment thread PLAN.md
Copilot finished work on behalf of jeduden May 1, 2026 09:23
Copilot finished work on behalf of jeduden May 1, 2026 12:50
@jeduden
jeduden merged commit 1a86b5c into main May 1, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants