task-verify

Runs project quality gates concurrently with automatic stack detection and records a verification artifact.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/real-case/marvin-toolkit --skill task-verify-real-case
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: task-verify
Source: https://github.com/real-case/marvin-toolkit/tree/main/plugins/marvin/skills/task-verify
Command: npx skills add https://github.com/real-case/marvin-toolkit --skill task-verify-real-case

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually running tests, linters, type checkers, and builds across different technology stacks is error-prone and inconsistent, and there is no reliable record proving code is ready to ship. This Skill automates quality gate execution and produces a verification artifact that gates delivery. ## Core Features & Use Cases - Automatic stack detection: Detects Go, Rust, Python, TypeScript, Java/Kotlin, C#/.NET, Swift, Ruby, PHP, and C/C++ from marker files, with a declared-command fallback (package.json scripts, Makefile targets) for any other stack. - Concurrent gate execution: Runs test, lint, type-check, and build gates in parallel by default, with sequential and fail-fast execution modes for resource-constrained environments. - Pipeline-aware verification: Supports feature, bug, and standalone modes, checking that new or regression tests exist and writing results to .marvin/task/verification.md that the delivery step reads. - Use Case: After finishing an implementation, ask to verify the project; the Skill runs all applicable gates, reports PASS, FAIL, or PASS WITH WARNINGS, and blocks delivery if tests fail. ## Quick Start Ask the assistant to verify the project and run all quality gates before delivering the current changes.

Frequently Asked Questions about task-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run tests, lint, and build checks automatically before shipping code?▼

Invoke the verification workflow, which auto-detects your stack from marker files like go.mod, Cargo.toml, or package.json and runs the applicable test, lint, type-check, and build gates concurrently. Results are recorded in a verification report that gates delivery.

What happens if my project uses a stack that is not auto-detected?▼

For stacks outside the built-in set, the tool falls back to commands the project declares itself, checking package.json scripts and then Makefile targets. If nothing is found, it reports an explicit no-gates-detected message rather than silently passing.

Can I override the default test or lint commands for my project?▼

Yes. Declare gate commands in .marvin/config.json, for example a gates object mapping test or lint to your preferred command. Overrides apply per gate, and unset gates still fall back to stack detection.

Does a failed test block code delivery?▼

Yes. A FAIL verdict blocks the delivery step by design, since the delivery gate reads the verification artifact and refuses to proceed. Warnings such as missing new tests produce a PASS WITH WARNINGS verdict that delivery surfaces for confirmation.

Can I run the gates sequentially instead of in parallel?▼

Yes. Pass the execution argument as sequential to run gates one at a time with lower peak CPU and memory, or fail-fast to stop at the first failure. Parallel execution is the default because it minimizes latency on the common passing path.