// Fix markdown linting and prettier formatting issues in markdown files
Manage local multigres cluster components (multipooler, pgctld, multiorch, multigateway) - start/stop services, view logs, connect with psql, test S3 backups locally
Generate a PR title and description from the current branch diff against main
Run unit tests, integration tests, and development tasks for multigres
| name | fix-markdown-lint |
| description | Fix markdown linting and prettier formatting issues in markdown files |
| disable-model-invocation | true |
Fix markdown lint errors and prettier formatting issues so CI passes.
/fix-markdown [file ...]
If no files are specified, auto-detect changed .md files:
git diff --name-only HEAD upstream/main -- '*.md'
Run markdownlint with the repo config to see all errors:
markdownlint-cli2 --config .github/linters/.markdownlint.json <files>
Read each file that has errors before fixing.
Apply fixes for each error type:
MD013 — Line length (max 120 chars, code blocks and tables exempt):
MD040 — Fenced code block language:
text for plain text, CLI output, or pseudo-code diagramsbash, go, json, yaml, sql, markdown) when the content is codeMD060 — Table column style:
| --- | --- | not |---|---|Other rules:
After fixing lint errors, run prettier to normalize formatting:
npx prettier --write <files>
Prettier will align tables, normalize spacing, and fix other formatting.
Re-run markdownlint to confirm all errors are resolved:
markdownlint-cli2 --config .github/linters/.markdownlint.json <files>
If errors remain, fix them and repeat until clean.
.github/linters/.markdownlint.json
.prettierrc)