@redocly/recheck 0.9.0 → 0.11.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@redocly/recheck",
-  "version": "0.9.0",
+  "version": "0.11.0",
   "description": "Content linting (configurable + built-in rules)",
   "type": "module",
   "main": "dist/index.js",
@@ -59,13 +59,22 @@
     "typescript": "6.0.3",
     "vitest": "4.1.10",
     "@redocly/portal": "0.68.3",
-    "@redocly/theme": "0.69.0-next.2"
+    "@redocly/theme": "0.69.0-next.5"
+  },
+  "nx": {
+    "targets": {
+      "vitest:test": {
+        "dependsOn": [
+          "build"
+        ]
+      }
+    }
   },
   "scripts": {
     "build": "tsgo && tsgo --noEmit -p tsconfig.typecheck.json",
     "dev": "tsgo --watch",
     "start": "node dist/cli.js",
-    "validate": "node dist/cli.js validate",
+    "validate": "node dist/cli.js --validate-config",
     "test": "nx run vitest:test",
     "examples:generate": "node scripts/generate-examples.mjs",
     "markdoc-schema:generate": "tsx scripts/generate-markdoc-schema.mjs",

package/skills/recheck-config/SKILL.md

@@ -17,7 +17,7 @@ Configure recheck for a project the way its maintainers would: measure first, de
    ```
 
    ```bash
-   npx recheck validate
+   npx recheck --validate-config
    ```
 
 2. Add prose rules deliberately, not wholesale.
@@ -28,7 +28,7 @@ Configure recheck for a project the way its maintainers would: measure first, de
 1. Run the whole corpus and count findings per rule:
 
    ```bash
-   npx recheck run docs --output json --annotations-limit 5000 --output-path findings.json
+   npx recheck docs --output json --annotations-limit 5000 --output-path findings.json
    ```
 
    Group the findings by `ruleName` and look at real examples of each before deciding anything.
@@ -53,7 +53,7 @@ Configure recheck for a project the way its maintainers would: measure first, de
 When the corpus has too many errors to fix at once, record them and gate only new ones:
 
 ```bash
-npx recheck baseline
+npx recheck --generate-baseline
 ```
 
 Commit `recheck-baseline.yaml` and add `baseline: recheck-baseline.yaml` to the config.
@@ -61,6 +61,6 @@ Counts only step down: when findings get fixed, regenerate the baseline and comm
 
 ## Finish
 
-- `npx recheck validate` must pass.
+- `npx recheck --validate-config` must pass.
 - Every `off` and every exception carries a comment with its reason.
 - The config's README section or the project docs say how contributors run recheck locally.

package/skills/recheck-lint/SKILL.md

@@ -18,13 +18,13 @@ If none exists, this skill does not apply.
 1. After you write or edit markdown files, run recheck on them:
 
    ```bash
-   npx recheck run <file-or-directory>
+   npx recheck <file-or-directory>
    ```
 
 2. If it reports errors, run the auto-fix first — most structural findings repair themselves:
 
    ```bash
-   npx recheck run <file-or-directory> --fix
+   npx recheck <file-or-directory> --fix
    ```
 
 3. Fix the remaining errors by hand.