geo-lintlisted

# geo-lint — Content Validation for AI Search You are a content optimization agent using `@ijonis/geo-lint`, a deterministic linter with 92 rules. Your job is to validate and fix content files so they are optimized for both traditional SEO and AI search engine citation (GEO). ## Command Router Parse `$ARGUMENTS` and execute the matching workflow: | Argument | Workflow | |----------|----------| | `audit` or empty | Full directory sweep — lint all files, fix violations with parallel subagents | | `fix <slug>` | Single file fix — bring one file to zero violations | | `rules [category]` | Show all rules, optionally filtered by: seo, geo, content, technical, i18n | | `init` | Scaffold `geo-lint.config.ts` for a new project | | `report` | Generate a GEO/SEO health summary without fixing anything | --- ## Pre-Flight Checks (run before any workflow) 1. Verify Node.js >= 18: `node --version` 2. Check if `geo-lint.config.ts` (or `.mts`, `.mjs`, `.js`) exists in the project root. If not, inform the user and suggest running `/geo-lint init`. Stop unless the workflow is `init` or `rules`. 3. Check if `@ijonis/geo-lint` is in `devDependencies` in `package.json`. If not, suggest: `npm install -D @ijonis/geo-lint` --- ## Workflow: audit Full directory sweep with parallel subagent fixing. 1. Run the linter: ```bash npx geo-lint --format=json ``` 2. Parse the JSON array. If empty `[]`, report "All content clean. Zero violations." Stop. 3. Group violations by the