smithery/alexago83

logics-doc-linter

Lint and validate the Logics Markdown conventions. Use when Codex should verify filenames, top headings, and required indicators across `logics/request`, `logics/backlog`, `logics/tasks`, `logics/product`, and `logics/architecture`, and report inconsistencies.

Installation

$ npx skills add smithery/alexago83 --skill logics-doc-linter

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/alexago83 · top by installs.

npx skills add smithery/alexago83

Browse all from smithery/alexago83

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,700 B
  • docs SUMMARY.md 244 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Lint Logics docs

Run

python logics/skills/logics-doc-linter/scripts/logics_lint.py
python logics/skills/logics-doc-linter/scripts/logics_lint.py --require-status

What it checks

  • Filename patterns (req###.md, item###.md, task###.md, prod###.md, adr###*.md).
  • First heading format: ## <doc_ref> - <Title>.
  • Required indicators:

- requests: From version, Understanding, Confidence - backlog/tasks: plus Progress

  • product briefs: Date, Status, related refs, Reminder
  • architecture docs: Date, Status, Drivers, related refs, Reminder
  • Status value validation when present using the allowed values for each doc family.
  • Optional strict mode (--require-status) to enforce Status on every supported doc type.
  • For modified or untracked workflow docs (request, backlog, task):

- blocking errors for critical indicator placeholders such as X.X.X and ??% - warning-level reporting for leftover template filler text such as Describe the need or Add context and constraints - warning-level reporting for generic Mermaid scaffolds or missing/stale %% logics-signature comments in workflow Mermaid blocks - if a doc edit is explicitly non-semantic, add a marker such as > Maintenance edit: or > Non-semantic edit: in the doc so the linter can keep indicators stable without guessing intent