一键在 Manus 中运行任何 Skill

logics-doc-linter

星标0

分支0

更新时间2026年4月12日 12:34

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.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

AlexAgo83

AlexAgo83/cdx-logics-kit

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

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

同仓库更多 Skills

同仓库

logics-progress-updater

AlexAgo83/cdx-logics-kit

Update Logics indicators consistently. Use when Codex should update request/backlog/task indicators (`From version`, `Understanding`, `Confidence`, `Progress`, `Complexity`, `Theme`) or companion doc indicators in `logics/product|architecture/*.md` such as `Date`, `Status`, `Drivers`, related refs, and `Reminder`.

2026-04-120

logics-flow-manager

AlexAgo83/cdx-logics-kit

Manage this repository's Logics workflow (logics/request -> logics/backlog -> logics/tasks) and keep companion product or architecture refs aligned: create new request/backlog/task docs, promote between stages, keep From version, Understanding, Confidence, and Progress indicators consistent, and generate correctly-numbered filenames. Use when a user asks to triage an idea, write a request, promote it to a backlog item, or create an executable task plan.

2026-04-120

logics-bootstrapper

AlexAgo83/cdx-logics-kit

Bootstrap the Logics directory structure in a new repository (create `logics/architecture`, `logics/product`, `logics/request`, `logics/backlog`, `logics/tasks`, `logics/specs`, `logics/external`) and add `.gitkeep` files for empty folders so the structure stays versioned. Use when setting up Logics in a fresh project or validating that required directories exist.

2026-04-100

logics-mermaid-generator

AlexAgo83/cdx-logics-kit

Generate Logics workflow Mermaid blocks with a deterministic fallback that stays compatible with the flow manager.

2026-04-090

logics-indexer

AlexAgo83/cdx-logics-kit

Generate a consolidated index of Logics documents. Use when Codex should build or refresh `logics/INDEX.md` summarizing requests, backlog items, and tasks with titles and progress.

2026-04-080

logics-relationship-linker

AlexAgo83/cdx-logics-kit

Build and maintain relationships across Logics documents. Use when Codex should discover or summarize links between `logics/request`, `logics/backlog`, `logics/tasks`, `logics/specs`, `logics/product`, and `logics/architecture` by scanning references and generating a relationship report.

2026-04-080

name	logics-doc-linter
description	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.

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