Name: vitepress-include-lint
Author: ahandsel

Imported from ahandsel/ahandsel.github.io (.github/skills/vitepress-include-lint/SKILL.md). Install upstream with npx skills add ahandsel/ahandsel.github.io --skill vitepress-include-lint. Copyright stays with the author.

VitePress include lint

Verify that every VitePress include directive is formatted and resolved correctly.

Quick start

Run the bundled checker from the repository root:

node skills/vitepress-include-lint/scripts/check-vitepress-includes.mjs --paths contents

What to validate

For each include directive line:

Enforce no space between <!-- and @include:.
Enforce no trailing space between the include path and -->.
Resolve the referenced path from the source markdown file directory and verify the target file exists.
Ignore fragment suffixes (for example #english) when checking file existence.

Workflow

Run the checker on requested files or directories.
Review findings as file:line:column entries.
If requested, fix only the reported directives and rerun until clean.

Bundled resources

scripts/check-vitepress-includes.mjs

Checks markdown files for include formatting and path validity.

Examples:

node skills/vitepress-include-lint/scripts/check-vitepress-includes.mjs --paths contents
node skills/vitepress-include-lint/scripts/check-vitepress-includes.mjs --paths contents/en contents/ja
node skills/vitepress-include-lint/scripts/check-vitepress-includes.mjs --paths contents --repo-root .

Install vitepress-include-lint and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "ahandsel-ahandsel-github-io-vitepress-include-lint", "kind": "skill", "name": "vitepress-include-lint", "description": "Verify VitePress markdown include directives (`@include:`) for strict comment formatting and valid target file paths. Use when users ask to check, lint, or validate `` usage across docs.", "publisher": "ahandsel", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Verify VitePress markdown include directives (`@include:`) for strict comment formatting and valid target file paths. Use when users ask to check, lint, or validate `` usage across docs." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/ahandsel/ahandsel.github.io", "path": ".github/skills/vitepress-include-lint/SKILL.md", "ref": "35b325438b69dfa7d579c06be5d43428bbb9ac4a", "url": "https://github.com/ahandsel/ahandsel.github.io/blob/35b325438b69dfa7d579c06be5d43428bbb9ac4a/.github/skills/vitepress-include-lint/SKILL.md", "key": "ahandsel/ahandsel.github.io/.github/skills/vitepress-include-lint/SKILL.md" } }, "instructions": "# VitePress include lint\n\nVerify that every VitePress include directive is formatted and resolved correctly.\n\n\n## Quick start\n\nRun the bundled checker from the repository root:\n\n```bash\nnode skills/vitepress-include-lint/scripts/check-vitepress-includes.mjs --paths contents\n```\n\n\n## What to validate\n\nFor each include directive line:\n\n1. Enforce no space between ``.\n3. Resolve the referenced path from the source markdown file directory and verify the target file exists.\n4. Ignore fragment suffixes (for example ", "cost": { "context_tokens": 321 } }

vitepress-include-lint

About