← ClaudeAtlas

task-verifylisted

Run project quality gates — tests, lint, type-check, and build — concurrently with automatic stack detection (Go, Rust, Python, TypeScript, Java/Kotlin, C#/.NET, Swift, Ruby, PHP, C/C++, plus a declared-command / npm-script / Makefile fallback for any other stack) and produce a verification.md artifact that gates delivery. Use when the user says "verify", "run the gates", "run tests and lint", "check the project", "is this green?", "/marvin:task-verify", "marvin verify", after finishing implementation, or as a standalone health check on a repo before handing off work.
real-case/marvin-toolkit · ★ 0 · AI & Automation · score 68
Install: claude install-skill real-case/marvin-toolkit
# Verify Run project quality gates with stack auto-detection. Verification gates delivery — `/marvin:task-deliver` refuses to proceed if verification fails. ## Core principle **Trust the tests, not the vibes.** Code that "looks right" isn't verified. Code that passes its test suite, linter, type checker, and build is verified. This phase runs all available quality gates and records the results. ## Input - None required (operates on current project state) - Pipeline context determines verification mode. If not set explicitly in conversation, **infer from spec**: 1. Call the `spec` MCP tool with `action: "list"` — it answers with the resolved spec directory and every spec in it, highest number first. Match by slug from conversation context, or take the first record when there is nothing to match on; do not sort a directory listing by eye 2. Fall back to `.marvin/task/spec.md` 3. Detect type: prefer the spec's frontmatter `type` (`feature`/`bugfix`); else infer from structure — a "Root Cause Analysis" section → bugfix, a "Chosen Approach" section → feature 4. If no spec found → standalone mode - Verification modes: - **Feature**: new tests must exist and pass - **Bug**: regression test must exist; all pre-existing tests pass - **Standalone** (no pipeline context): run all checks, report results ## Workflow ### 1. Run the gates via the `verify` tool Call the **`verify` MCP tool** (`mcp__plugin_marvin_marvin__verify`). It owns stack detection and gate executi