dxverify

Automate full project quality verification pipelines across multiple software toolchains.

3|2|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/mitchellfyi/dex --skill dxverify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dxverify
Source: https://github.com/mitchellfyi/dex/tree/main/skills/dxverify
Command: npx skills add https://github.com/mitchellfyi/dex --skill dxverify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious, error-prone manual work of running scattered quality checks across different project toolchains, ensuring all verification steps are completed consistently before commits or pull requests.

Core Features & Use Cases

  • Auto-Toolchain Discovery: Automatically detects the project's quality tools (Make, npm, Cargo, pip, Go, etc.) and their corresponding commands, requiring no manual configuration for most standard development stacks.
  • Ordered Verification Pipeline: Runs format, lint, type-check, code generation, and test checks in the optimal sequence, with built-in fix-and-retry logic to resolve common failures automatically.
  • Use Case: After finishing a bug fix in a Node.js monorepo, use this Skill to run ESLint, TypeScript type checks, and Jest tests scoped to the changed package, fix any lint errors, and verify the changes are PR-ready.

Quick Start

Use the dxverify skill to run the full quality verification pipeline for your current project after you finish making code changes.

Frequently Asked Questions about dxverify

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

FAQPage Schema
How do I automate pre-commit quality checks across different project toolchains?

Automating pre-commit quality checks requires discovering and executing format, lint, type-check, and test pipelines. This Skill auto-detects toolchains like Make, Node.js, Rust, Python, Go, and PHP to run ordered verification steps consistently before code merges.

What is the best way to run linting and type checking before pushing code in a monorepo?

Running linting and type checking in a monorepo is handled by an ordered verification pipeline that scopes checks to changed packages. It executes formatting, lint rules, type safety, and tests with built-in fix-and-retry logic to ensure changes are PR-ready.

Does this code verification tool support Python and Go projects without manual configuration?

Yes, code verification supports Python and Go projects without manual configuration through auto-toolchain discovery. It automatically detects package managers like pip and Go modules, identifies their corresponding quality commands, and executes the full verification pipeline.

How to verify code generation freshness and test suite pass rates before a pull request?

To verify code generation freshness and test pass rates, run the full project quality verification pipeline. It sequences format, lint, type-check, code generation, and test checks in the optimal order to enforce consistent quality gates before merging code.

Why does my post-implementation quality check fail to catch formatting standard violations?

Post-implementation quality checks may miss formatting violations if the pipeline sequence is incorrect. This Skill enforces formatting standards first, followed by lint rules, type safety, and tests, applying fix-and-retry logic to resolve common failures automatically.