devflow-check
npx machina-cli add skill docutray/docutray-claude-code-plugins/devflow-check --openclawDevFlow: Quality Validation Flow
Execute all project validations in parallel using specialized subagents, providing structured reporting of results.
When to Use
Use this flow when you need to:
- Validate code quality before PR
- Check project health
- Run all tests and validations
- Verify build integrity
- Ensure no regressions
Flow Diagram
flowchart TD
A([BEGIN]) --> B[Parse arguments: --fast, --verbose]
B --> C[Load project validation config]
C --> D[Identify enabled validations]
D --> E{Fast mode?}
E -->|Yes| F[Skip build validation]
E -->|No| G[Include all validations]
F --> H[Launch parallel subagents]
G --> H
H --> I[test-runner: Execute tests]
H --> J[lint-runner: Execute linting]
H --> K[typecheck-runner: Type check]
H --> L{Fast mode?}
L -->|No| M[build-runner: Execute build]
L -->|Yes| N[Skip build]
I --> O[Collect JSON responses]
J --> O
K --> O
M --> O
N --> O
O --> P[Aggregate results]
P --> Q{All passed?}
Q -->|No| R{Verbose mode?}
R -->|Yes| S[Show full error details]
R -->|No| T[Show summary with fix recommendations]
Q -->|Yes| U[Generate success report]
S --> V([END])
T --> V
U --> V
Node Details
1. Load Configuration
Read .claude/details/commands/check.md for project-specific validation commands.
2. Parallel Execution
Launch all validation subagents simultaneously:
- Tests: Run complete test suite
- Linting: Code quality checks
- Type Checking: Language-specific type validation
- Build: Compile project (unless --fast)
3. Result Aggregation
Each subagent returns structured JSON:
{
"validation": "tests",
"status": "success|warning|error",
"duration": 12.3,
"summary": "145 tests passed",
"details": "...",
"errors": [],
"warnings": []
}
4. Executive Report
Generate consolidated summary with:
- Status per validation
- Execution time
- Error/warning count
- Recommended actions
Parameters
--fast: Skip build validation (quicker)--verbose: Show full output from all validations
Example Usage
/flow:devflow-check
/flow:devflow-check --fast
/flow:devflow-check --verbose
Output
Executive summary table:
┌─────────────────┬─────────┬─────────┬──────────────────────┐
│ Validation │ Status │ Time │ Result │
├─────────────────┼─────────┼─────────┼──────────────────────┤
│ 🧪 Tests │ ✅ OK │ 12.3s │ 145 passed │
│ 🔍 Linting │ ⚠️ WARN │ 3.4s │ 3 warnings │
│ 📝 Type Check │ ✅ OK │ 8.5s │ No type errors │
│ 🏗️ Build │ ✅ OK │ 45.2s │ Success │
└─────────────────┴─────────┴─────────┴──────────────────────┘
Source
git clone https://github.com/docutray/docutray-claude-code-plugins/blob/main/.kimi/skills/devflow-check/SKILL.mdView on GitHub Overview
DevFlow executes tests, linting, type checking, and build in parallel to assess code quality and project health. It loads a project-specific validation config, runs enabled validations, and reports a consolidated executive summary for quick insights.
How This Skill Works
The flow loads configuration from .claude/details/commands/check.md, then launches parallel subagents for tests, linting, type checking, and (unless --fast is used) build. Each subagent returns structured JSON which is aggregated into a single executive report highlighting status, duration, and actionable details.
When to Use It
- Validate code quality before PR
- Check project health
- Run all tests and validations
- Verify build integrity
- Ensure no regressions
Quick Start
- Step 1: /flow:devflow-check
- Step 2: Optional: /flow:devflow-check --fast or --verbose
- Step 3: Review the executive report and address any failures
Best Practices
- Ensure .claude/details/commands/check.md exists and reflects current project commands
- Use --fast for quick feedback when a full build isn’t required
- Use --verbose to surface full error details during debugging
- Review the aggregated results before merging or releasing
- Integrate this flow in CI as a PR/check step
Example Use Cases
- Pre-PR quality gate to catch issues early
- CI pipeline step that validates tests, linting, type checks, and build on each merge
- Post-dependency upgrade verification to detect regressions
- Local health check after a major refactor
- Nightly health sweep to identify flaky or failing validations