Fix README LICENSE link to explicit relative path

CodeSigils · CodeSigils · commit 390ed671a10a · 2026-05-12T16:11:16.000+03:00
diff --git a/README.md b/README.md
@@ -38,344 +38,10 @@ Learn more: See [AGENTS.md](AGENTS.md) for the full behavioral contract.
 
 ---
 
-## Design Philosophy
-
-This skill treats Markdown linting as **agent-safe repository governance**:
-
-- Formatting must be deterministic and idempotent
-- Fenced code blocks are safety boundaries and must not be rewritten as prose
-- Table formatting preserves semantic alignment (`:---`, `---:`, `:---:`)
-- `lint.js` is the canonical entry point for manual, CI, and agent-driven execution
-- Documentation, config, formatter behavior, and governance claims must stay synchronized
-
----
-
-## For End Users
-
-### Prerequisites
-
-Before installing, ensure your environment meets the following requirements:
-
-- **Hermes CLI** — Required to install the skill. The `post-write.js` hook is an optional safety net.
-- **Node.js (v18+)** — The linting pipeline relies on native Node.js scripts and `npx` to dynamically fetch `markdownlint-cli2` without requiring global installations.
-- **Cross-Platform** — The pipeline runs natively on Linux, macOS, and Windows. No WSL or Git Bash required!
-
-### Install the Skill
-
-```text
-hermes skills install CodeSigils/hermes-markdown-lint-skill/markdown-lint --force
-```
-
-The `--force` flag is required because the security scanner flags post-write hooks as dangerous (expected for a linting skill).
-
-### Post-Install: Hook (Optional Safety Net)
-
-The skill already instructs the AI agent to automatically lint every markdown file it writes. For guaranteed enforcement even if the agent skips the instruction, you can add a system-level hook:
-
-**Edit `~/.hermes/config.yaml`:**
-
-```yaml
-hooks:
-  post_tool_call:
-    - matcher: "write_file"
-      command: "node ~/.hermes/skills/markdown-lint/scripts/post-write.js"
-hooks_auto_accept: true
-```
-
-Restart Hermes for the hook to activate. This is **optional** — the mandatory lint rule in `SKILL.md` handles the common case.
-
-### Quick Start
-
-```bash
-# One-liner (recommended — pure Node.js, cross-platform)
-node ${HERMES_SKILL_DIR}/lint.js <path>
-
-# Options
-node ${HERMES_SKILL_DIR}/lint.js --check <path>     # Read-only check
-node ${HERMES_SKILL_DIR}/lint.js --all <dir>        # Fix all .md in directory
-node ${HERMES_SKILL_DIR}/lint.js --validate <path>  # Validate table column consistency
-node ${HERMES_SKILL_DIR}/lint.js --fences <path>    # Check fenced code blocks
-```
-
-Or run steps manually:
-
-```bash
-node skills/markdown-lint/references/format-tables.js <path> && npx markdownlint-cli2 --config skills/markdown-lint/references/.markdownlint.json <path> --fix
-```
-
-Step 1 formats all tables in a single pass (fixes separators + pads cells).
-Step 2 fixes everything else.
-
-### Preventing Broken Tables
-
-The most common table error is **column count mismatch** between the header, separator, and data rows. This often happens with:
-
-- Extra `|` characters in type definitions (e.g., `"tab" | "space"`)
-- Copy-paste errors in separator rows
-
-#### Validate Before You Push
-
-```bash
-# Add to CI or pre-commit to catch broken tables
-node lint.js --validate .
-```
-
-This validates:
-
-- Header columns match separator columns
-- All data rows have the correct number of columns
-- Pipes inside cells are properly escaped with `&#124;`
-
-#### How to Escape Pipes in Tables
-
-If a table cell contains a pipe character, escape it to prevent column misparsing:
-
-**Before (broken)** — the raw `|` breaks the column count:
-
-```markdown
-| Type    | Value |
-| :------ | :---- |
-| Options | "tab" | "space" |
-```
-
-**After (fixed)** — escape with `&#124;`:
-
-```markdown
-| Type    | Value                |
-| :------ | :------------------- |
-| Options | "tab" &#124; "space" |
-```
-
-### What It Does
-
-The pipeline (`format-tables.js` → `markdownlint-cli2`) fixes GFM violations automatically:
-
-**Table separators** — normalizes raw dashes to GFM-compliant aligned separators while preserving semantic alignment:
-
-Before:
-
-```markdown
-| Name  | Age  | Score |
-| ---   | ---: | :---: |
-| Alice | 25   | A     |
-```
-
-After:
-
-```markdown
-| Name  | Age | Score |
-| :---- | --: | :---: |
-| Alice |  25 | A     |
-```
-
-**Headings** — adds required blank lines around headings:
-
-Before:
-
-```markdown
-Some text
-## My Heading
-More text
-```
-
-After:
-
-```markdown
-Some text
-
-## My Heading
-
-More text
-```
-
-**Tabs & blank lines** — converts tabs to spaces and collapses multiple blank lines to one.
-
-### Configuration
-
-The skill includes a bundled config at `references/.markdownlint.json`.
-`lint.js` uses it automatically — no setup required.
-
-Key policy choices:
-
-- MD040 is disabled — blank fences are allowed for output examples
-- MD055 is disabled — leading/trailing table pipes are optional
-- MD060 is set to `aligned` — table column positions are normalized while preserving semantic alignment
-
-### Testing
-
-Run against the test fixture:
-
-```bash
-npx markdownlint-cli2 --config skills/markdown-lint/references/.markdownlint.json test/kitchensink.md
-```
-
-### CI / Pre-commit
-
-The project uses GitHub Actions to validate every push and PR. You can run the same checks locally:
-
-```bash
-# 1. Repository governance/config consistency
-node scripts/check-consistency.js
-
-# 2. Unit tests for the table formatter
-node test/format-tables.test.js
-
-# 3. Check for unclosed code fences or bad closers
-node lint.js --fences .
-
-# 4. Validate table column consistency
-node lint.js --validate .
-
-# 5. Final lint check
-node lint.js --check .
-```
-
-Pre-commit:
-
-```yaml
-# .pre-commit-config.yaml
-- repo: https://github.com/pre-commit/pre-commit-hooks
-  hooks:
-    - id: markdownlint
-```
-
----
-
-## Official Hermes Skills Documentation
-
-Learn more about creating and managing Hermes skills:
-
-- [Creating Skills](https://hermes-agent.nousresearch.com/docs/developer-guide/creating-skills) - Official guide
-- [Skills User Guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/skills) - Using skills
-- [agentskills.io](https://agentskills.io) - Open standard (compatible with Claude, OpenAI, etc.)
-
----
-
-## For Developers
-
-### Skill Structure
-
-```text
-.
-├── AGENTS.md
-├── lint.js                      # Developer wrapper
-├── README.md
-├── scripts/
-│   └── check-consistency.js     # Config/docs anti-drift checker
-├── skills/
-│   └── markdown-lint/           # <-- The actual skill payload
-│       ├── SKILL.md
-│       ├── lint.js              # Canonical entry point
-│       ├── scripts/
-│       │   ├── check-fences.js  # Fenced code block checker
-│       │   └── post-write.js    # Auto-lint hook (optional)
-│       └── references/
-│           ├── format-tables.js # Single-pass table formatter
-│           └── .markdownlint.json
-└── test/
-    └── format-tables.test.js
-```
-
-### Key Changes in v2.9.1
-
-- Corrected MD014 and MD041 configuration drift.
-- Set MD060 to `aligned` to match formatter behavior.
-- Added `scripts/check-consistency.js` to prevent config/docs drift.
-- Added GitHub Actions CI for consistency, formatter tests, fence validation, table validation, and final lint checks.
-- Clarified agent governance and deterministic formatting philosophy.
-
-### Key Changes in v2.9
-
-- Replaced `jq` dependency with zero-dependency Node.js extraction in `post-write.js`.
-- Replaced brittle bash regex `check-fences.sh` with a native `check-fences.js` script.
-- Significantly improved `lint.js` bulk execution performance (node processes run once instead of per-file).
-- **Refactored entirely to pure Node.js**: Replaced `lint.sh` and `post-write.sh` bash wrappers with native `.js` scripts. The pipeline is now 100% cross-platform (Windows native) and immune to `chmod +x` permission denied errors.
-- **Single-pass table formatting**: Merged `fix-tables.js` + `pad-tables.js` into `format-tables.js` — halves I/O per file.
-
-### Key Changes in v2.8
-
-- Add `--fences` mode to `lint.js` for fenced code block validation
-- Add `scripts/check-fences.js` — validates code fences natively in Node.js
-- Disable MD055 (table-pipe-style) — no longer enforces leading/trailing `|` on tables
-- Disable MD033 (no-inline-html) — inline HTML is allowed in GFM
-- Sync `skills/markdown-lint/lint.js` with root `lint.js` (all flags now available)
-
-### Key Changes in v2.7
-
-- Add `--validate` mode to `format-tables.js` and `lint.js` to catch table column mismatches
-- Add "Preventing Broken Tables" section with escaped pipe guidance
-
-### Key Changes in v2.6
-
-- Add Node.js hook `scripts/post-write.js` for auto-lint on write_file
-- Add to `~/.hermes/config.yaml` to enable auto-lint
-- Enable MD032 (blanks-around-lists) — lists must be surrounded by blank lines
-- Enable MD060 (table-column-style) — table pipes must align with header content
-- Add `hooks_auto_accept: true` for silent auto-lint on write
-
-### Key Changes in v2.5
-
-- Disable MD040 (fenced-code-language) and MD055 (table-pipe-style) — too strict for prose
-- Fix column alignment to match VSCode/marktext format (header.length - 1)
-- Remove glob dependency, use recursive fs.walk instead
-
-### Key Changes in v2.4
-
-- Enable MD030 (list-marker-space) — strict GFM compliance
-
-### Key Changes in v2.3
-
-- Add `lint.js`: self-contained Node.js entry point that resolves npx across environments
-  (PATH, corepack, nvm, fnm) — no PATH dependency for end users
-
-### Key Changes in v2.1
-
-- Migrated to Node.js stack (fix-tables.js instead of fix-tables.py)
-- Added auto-width column alignment for tables
-- Added MD060, MD025, MD032 disabled rules
-- Removed duplicate configuration
-- Updated frontmatter to Hermes 2.x format
-
-### GitHub PR Workflow
-
-This skill supports the full GitHub PR lifecycle via the `github-pr-workflow` skill:
-
-```bash
-# 1. Create a feature branch
-git checkout -b feat/your-feature-name
-
-# 2. Make changes and commit
-git add <files>
-git commit -m "feat: description of changes"
-
-# 3. Push and create PR
-git push -u origin HEAD
-gh pr create --title "feat: your feature" --body "## Summary..."
-```
-
-### Adding to Your Own Tap
-
-```bash
-# Fork this repo or copy the skills/ directory into your repo
-# Your tap repo structure must be: <repo>/skills/<skill-name>/SKILL.md
-
-# Then add your tap
-hermes skills tap add your-username/your-skills-repo
-```
-
-### Inspect Before Installing
-
-```bash
-hermes skills tap add CodeSigils/hermes-markdown-lint-skill
-hermes skills inspect CodeSigils/hermes-markdown-lint-skill/markdown-lint
-```
-
----
-
 ## Skill Documentation
 
 See [skills/markdown-lint/SKILL.md](skills/markdown-lint/SKILL.md) for the full skill document.
 
 ## License
 
-MIT License. See [LICENSE).
+MIT License. See [LICENSE](./LICENSE).
