[docs] Fix pre-existing markdownlint errors across 7 files#215
Merged
justfinethanku merged 1 commit intoApr 21, 2026
Conversation
Auto-run: markdownlint-cli2 --fix --config .github/.markdownlint.jsonc Manual: 2 MD028 in life-engine/README.md (HTML comment separator) Brings `markdown-lint` CI check from 55 pre-existing errors to 0. Files: - recipes/adaptive-capture-classification/README.md - recipes/adaptive-capture-classification/classifier_prompt.md - recipes/life-engine/README.md - recipes/life-engine/life-engine-skill.md - recipes/ob-graph/README.md (same fix as PR NateBJones-Projects#210; harmless duplicate) - recipes/obsidian-vault-import/README.md - recipes/vercel-neon-telegram/README.md - schemas/workflow-status/README.md No content changes. Pure formatting: blank lines around fences/headings, HTML-comment separators between adjacent blockquotes, list-indent/ numbering normalization. Precedent: PR NateBJones-Projects#161 did the same for 15 files.
github-actions
Bot
added
recipe
alanshurafa
added a commit
to alanshurafa/OB1
that referenced
this pull request
Apr 21, 2026
Add a non-blockquote line between two adjacent GitHub alert callouts so markdownlint stops treating them as one blockquote with a blank line inside. Restores a clean run on recipes/atomizer/README.md. The rest of the repo-wide Markdown Lint failure is pre-existing and covered by a separate cleanup PR (tracker in MEMORY, pattern matches NateBJones-Projects#161/NateBJones-Projects#215).
This was referenced Apr 22, 2026
gleesonb
pushed a commit
to gleesonb/OB1
that referenced
this pull request
May 12, 2026
…lanshurafa/markdownlint-cleanup [docs] Fix pre-existing markdownlint errors across 7 files
alanshurafa
added a commit
to alanshurafa/OB1
that referenced
this pull request
May 19, 2026
Add a non-blockquote line between two adjacent GitHub alert callouts so markdownlint stops treating them as one blockquote with a blank line inside. Restores a clean run on recipes/atomizer/README.md. The rest of the repo-wide Markdown Lint failure is pre-existing and covered by a separate cleanup PR (tracker in MEMORY, pattern matches NateBJones-Projects#161/NateBJones-Projects#215).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
The
Markdown LintCI workflow lints**/*.mdacross the whole repo on every PR, not just PR-changed files. As of 2026-04-18, it reports 55 pre-existing errors across 6 files that pre-date any of my in-flight PRs (#204–#214). This makes the CI status ambiguous for every open PR — reviewers can't distinguish "lint fail because this PR introduced errors" from "lint fail because pre-existing errors."PR #161 set the precedent for handling this class of cleanup separately. This PR applies the same pattern to the current batch of pre-existing errors.
What this changes
Applied `markdownlint-cli2 --fix --config .github/.markdownlint.jsonc` across the entire repo. 53 of 55 errors were auto-fixable. Remaining 2 (MD028 blank-line-in-blockquote in `life-engine/README.md`) were fixed manually with the standard HTML-comment-separator (``) pattern used by markdownlint when separate blockquotes need to coexist.
No content changes. Pure formatting:
Files touched (8)
Verification
```bash
npx markdownlint-cli2 --config .github/.markdownlint.jsonc "**/*.md" "#node_modules"
Summary: 0 error(s)
```
With this merged, `Markdown Lint` CI should return to green on all 11 of my in-flight PRs (once they rebase onto the new main).
Review
Static-reviewed before push. Pure formatting with zero semantic change. Easy to eyeball the diff — 53 insertions, 12 deletions, all line-level whitespace / separator additions.