← ClaudeAtlas

task-auditlisted

Read-only lint of the whole spec corpus under .marvin/task — duplicate spec numbers, numbering holes, slug collisions, dangling depends_on references, unsealed specs, statuses outside the pipeline vocabulary, and files that do not identify themselves as specs. Use when the user says "audit the specs", "lint the spec corpus", "check .marvin/task", "are there duplicate spec numbers?", "do any specs depend on something that doesn't exist?", "which specs are unsealed?", or wants the spec directory checked before starting the next task. Renders the spec tool's findings with per-class remediation guidance; changes nothing. Not for decision records (adr-audit), code health (refactor-audit), or vulnerabilities (sec-scan).
real-case/marvin-toolkit · ★ 0 · AI & Automation · score 68
Install: claude install-skill real-case/marvin-toolkit
# Task Audit Corpus-wide consistency lint for the project's task specs. The checks are deterministic and live in the **`spec` MCP tool**; this skill runs them, renders the findings with remediation guidance, and **changes nothing** — every fix is the user's move. ## Input `$ARGUMENTS` — optional focus (e.g. a finding class like "unsealed specs", or "errors only"). The audit always runs corpus-wide; a focus narrows what you expand on. ## Workflow ### 1. Run the audit Call the `spec` MCP tool from the `marvin` server with `{"action": "audit"}`. It resolves the spec directory the same way the rest of the pipeline does (config → detection → `.marvin/task`), reads every spec in it, and returns typed findings with severities: **errors** fail the audit, **warnings** inform. The call takes no spec file and no other argument. Do not pass `specPath` or `specContent` — the audit is about the corpus, not about one spec. ### 2. Render findings with remediation Present the tool's report, then add a remediation note per finding class that actually occurred — grouped, errors first: | Class | Severity | What it means | Remediation | |-------|----------|---------------|-------------| | `malformed` | error | The file is in the spec directory but does not identify itself as a spec — frontmatter missing `slug`, `type`, `status` or `created` (including a file with no frontmatter block at all), or a file the reader could not read | Give the file frontmatter carrying all four keys, or move