{"id":76483,"plugin_id":"plugin_asdk_app_6ad620393af88191af4aafc6d67d3780","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-02T18:12:27.397Z","digest":"6bb3e4cf6db573b4b336a01040be6f22505ec3516b8886a13ff16591e30c1de0","against":null,"payload":{"description":"Use when you write or edit Markdown in a project whose redocly.yaml has a recheck block or a recheck/* preset in extends — run redocly recheck on the touched files before you commit them or hand them over, and fix what it finds.","included_files":[],"name":"recheck-lint","skill_md_contents":"---\nname: recheck-lint\ndescription: Use when you write or edit Markdown in a project whose redocly.yaml has a recheck block or a recheck/* preset in extends — run redocly recheck on the touched files before you commit them or hand them over, and fix what it finds.\n---\n\n# Lint Markdown with recheck before you commit it\n\nThis project lints Markdown structure and prose with `redocly recheck`.\nYour Markdown must pass it, the same as code must pass its tests.\n\n## When this applies\n\nLook for a `redocly.yaml` in the project root or above the files you touched.\nThis skill applies when that file has a `recheck` block, or a `recheck/*` preset in its root `extends`, for example:\n\n```yaml\nextends:\n  - recommended\n  - recheck/markdown\nrecheck:\n  rules:\n    recheck/line-length: off\n```\n\nIf neither exists, skip this skill.\nThe command checks nothing in that case and says so.\n\n## What to do\n\n1. After you write or edit Markdown files, run recheck on them:\n\n   ```bash\n   npx @redocly/cli recheck <file-or-directory>\n   ```\n\n   Pass the files you touched, not the whole repository, so the report is yours to act on.\n\n2. If it reports errors, run the auto-fix first — most structural findings repair themselves:\n\n   ```bash\n   npx @redocly/cli recheck <file-or-directory> --fix\n   ```\n\n   The command lists every edit it made.\n   Read the list: a fix inside a Markdoc tag body or a code sample deserves a look.\n\n3. Fix the remaining errors by hand.\n   Read each message; the rule name links the finding to its intent.\n   To see one rule at a time, add `--rule=<name>` with the name the report prints.\n\n4. Re-run until it reports no errors, and only then commit or output the content.\n   The command exits with code 1 while errors remain.\n\n## Rules of conduct\n\n- Fix content instead of suppressing findings.\n  Suppress only a true positive that must stay as written, with an inline directive on that one line:\n\n  ```markdown\n  <!-- recheck-disable-next-line recheck/rule-name -->\n  ```\n\n  Name the rule by its full key or by the short name the report prints.\n  Never disable a rule project-wide to make your change pass, and never edit the `recheck` block to get past a finding.\n\n- Warnings and info findings do not block you.\n  Leave them unless the task asks for cleanup.\n- If a `.redocly.recheck-baseline.yaml` file sits next to `redocly.yaml`, the baseline already covers old findings; only new findings are yours to fix.\n  Do not run `--generate-baseline` to absorb findings your change introduced.\n  If your change removed old findings, the run reports stale baseline entries; regenerate the baseline then, and commit the smaller file with your change.\n- A finding you believe is a false positive is worth reporting to the maintainer, not silently suppressing.\n- Do not add `markdownlint` or `vale` comments.\n  Recheck does not read them.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}