devflow-check

Name: devflow-check
Availability: InStock
Author: docutray

Run tests, linting, type checks, and builds in parallel.

2|1|Updated Oct 27, 2025

Search Tags:#validation #build #parallel #lint #ci #tests #type-check

Ready to run

npx skills add https://github.com/docutray/docutray-claude-code-plugins --skill devflow-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: devflow-check
Source: https://github.com/docutray/docutray-claude-code-plugins/tree/main/.kimi/skills/devflow-check
Command: npx skills add https://github.com/docutray/docutray-claude-code-plugins --skill devflow-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual, sequential validations of code quality slow down feedback and increase risk of missed issues.

Core Features & Use Cases

Parallel execution of tests, linting, type checking, and builds to speed up validation.
Configurable via flags such as --fast and --verbose to tailor feedback and verbosity.
Use Case: when preparing a PR or release, run all checks in one pass to obtain a comprehensive health report.

Quick Start

Invoke the devflow-check flow to run all validations in parallel and obtain a concise executive report.

Frequently Asked Questions about devflow-check

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

FAQPage Schema

How do I run tests, linting, and type checks in parallel to speed up CI feedback?▼

To run tests, linting, and type checks in parallel, you can orchestrate project health validations simultaneously instead of sequentially. This speeds up CI-like workflows by executing all checks in one pass and aggregating the results into a comprehensive report.

What is the best way to validate software quality before preparing a pull request?▼

The best way to validate software quality before a PR is to run parallel validations across your codebase. This approach executes tests, linting, type checks, and builds concurrently, providing an executive report to ensure comprehensive project health before submission.

Can I use a fast mode to get quicker validation feedback on my builds?▼

Yes, you can use a fast mode to get quicker validation feedback on your builds. Configurable flags allow you to tailor the validation process, enabling fast mode to reduce execution time or verbose output to gain detailed insights into the checks.

Does parallel execution work for both build and type checking processes?▼

Yes, parallel execution works for both build and type checking processes. The orchestration applies to CI-like workflows across tests, linting, type checks, and builds, verifying software quality by running these validations simultaneously rather than sequentially.

How do I get detailed insights when my linting or type checks fail?▼

To get detailed insights when linting or type checks fail, you can enable verbose output during the validation process. This provides detailed insights and aggregated results in the structured executive report, helping you identify specific issues quickly.

Why does sequential validation slow down code quality checks and increase risk?▼

Sequential validation slows down code quality checks by processing tests, linting, and builds one after another, which delays feedback. This manual approach increases the risk of missed issues, whereas parallel execution aggregates results instantly to verify project health.