skills.rest
edonghyun
edonghyunCOMMUNITY
Explore all skills by this author →
GitHub

lint

Audit the specs directory for hygiene issues and write a structured report to specs/LINT.md.

1|Updated May 19, 2026
Search Tags:#markdown#auditing#hygiene#lint#specs#cross-references
One-click install
npx skills add https://github.com/edonghyun/donghyuns-agent-tools --skill lint-edonghyun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lint
Source: https://github.com/edonghyun/donghyuns-agent-tools/tree/main/plugins/spec-mirror/skills/lint
Command: npx skills add https://github.com/edonghyun/donghyuns-agent-tools --skill lint-edonghyun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill catches structural and hygiene problems in specs before they become broken safety nets, helping teams trust their documentation again.

Core Features & Use Cases

  • Audits cross references, source lines, anchor collisions, and preserved blocks in layered spec files.
  • Flags stale inference markers, broken refs links, invalid acceptance criteria, and stub collection mismatches.
  • Use it after manual edits to spec files, before relying on generated specs in CI, or when a spec report looks incomplete or inconsistent.

Quick Start

Ask the lint skill to audit the specs directory and write a spec hygiene report to specs/LINT.md.

Frequently Asked Questions about lint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check markdown specs for broken cross references and dead links?▼

To check markdown specs for broken cross references and dead links, you can audit the specs directory to verify internal hygiene and output a structured report to specs/LINT.md without modifying source files.

What is the best way to automate spec maintenance validation before running CI checks?▼

Automating spec maintenance validation before CI checks involves auditing the specs directory for structural drift, invalid line targets, and stale markers, then writing the results to a dedicated LINT.md report.

How do I detect orphaned keep blocks and stale inference markers in spec files?▼

Detecting orphaned keep blocks and stale inference markers in spec files requires an auditing process that scans the specs directory for internal hygiene issues and flags invalid or outdated preserved blocks.

Do I need to install any dependencies to validate acceptance criteria quality in specs?▼

No dependencies are required to validate acceptance criteria quality in specs, as this hygiene auditing capability operates independently to check for stub collection mismatches and write a structured report.

Can I validate anchor collisions and source refs without modifying my existing spec files?▼

Yes, you can validate anchor collisions and source refs without modifying existing spec files, because the auditing process explicitly writes exclusively to specs/LINT.md and leaves all other spec files untouched.

Why does my spec report look incomplete after manual edits to the specs directory?▼

A spec report may look incomplete after manual edits due to spec drift, which includes broken refs links, dead links, and invalid acceptance criteria that an internal hygiene audit can identify and report.

Related Skills

Explore More Software Engineering Skills→
softwareByAndisoftwareByAndi

manage-specs

Audit and update specification files in the specs/ directory.

Community
Advanced
DavidROliverBADavidROliverBA
49

check-weblinks

Check vault weblinks and classify them as active, redirected, dead, or error.

Community
Intermediate
epieczkoepieczko

hook.register

Validate and register hook manifest files into the Hook Registry.

Community
Intermediate
timsvoicetimsvoice

specimin-ui-accessibility

Audit and fix generated UI code for WCAG 2.1 AA compliance.

Community
Advanced