spec-lint
Check a repository's specification (`docs/spec/`) against its conventions before a specification change merges: trace comments, status markers that cite an existing task, decision or issue, lock marke
SKILL.mdskills/spec-lint/SKILL.md
GitHubspec-lint
Read-only. Report each finding as file:line: problem; fix nothing unless asked.
- Every SDD requirement is a
**XX-nn.**line followed by its<!-- id: SDD-XX-nn | tdd: ... | status: ... -->comment, and every TDD item is a#### TDD-x.y.zheading followed by its<!-- id: ... | implements: ... -->comment, as the conventions at the top ofSDD.mdandTDD.mdstate.tdd:andimplements:cite items that exist. - Every status is
implemented,pending:#Nordeviation:#N, and#Nresolves: in a local repository (tasks kept as files) to a file indocs/tasks/ordocs/tasks/done/; in a GitHub-backed one to an issue (gh issue view N). Apendingitem whose task is done, or whose issue is closed, is a finding. - Where the specification already uses spec-lock markers, every subsection carries one. A specification with none is not a finding.
- No section names a person, agent, model, session or process history.
- Every
Describes release:header matches the current tag or candidate. - In a local repository, every file in
docs/tasks/carries aScope:line and aDepends on:line, andloop tasks checkreports ok where theloopcommand is installed.