midnight-cq:quality-check

Run and interpret linting, type checking, contract compilation, and test failures for Midnight projects.

37|9|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/devrelaicom/midnight-expert --skill midnight-cq-quality-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: midnight-cq:quality-check
Source: https://github.com/devrelaicom/midnight-expert/tree/main/plugins/midnight-cq/skills/quality-check
Command: npx skills add https://github.com/devrelaicom/midnight-expert --skill midnight-cq-quality-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill centralizes running, interpreting, and fixing code quality checks for Midnight Compact projects so developers spend less time triaging Biome, TypeScript, compiler, and test failures and more time shipping code.

Core Features & Use Cases

  • Unified diagnostics: Explains how to read Biome, tsc, compact compiler, Vitest, and Playwright outputs and where to look in source and generated artifacts.
  • Actionable fixes: Provides the common command sequences and quick remedies such as auto-formatting, re-compiling contracts, and reproducing full CI runs to resolve errors.
  • CI and edge-case guidance: Covers practical troubleshooting for SKIP_ZK, compact compiler and runtime version mismatches, Node version alignment, caching issues, and Playwright browser installation.

Quick Start

Run the full pre-push quality suite from the project root by running biome ci then tsc --noEmit and vitest run to reproduce and fix failures.

Frequently Asked Questions about midnight-cq:quality-check

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

FAQPage Schema
How do I fix lint, type, and test failures in Midnight Compact projects?

Fix Midnight Compact failures by running biome ci, tsc --noEmit, and vitest run from the project root to reproduce CI errors, then apply actionable remedies like auto-formatting, recompiling contracts, or adjusting Node versions.

What is the best way to troubleshoot compact compiler and runtime version mismatches?

Troubleshoot compact compiler and runtime version mismatches by checking Node version alignment and verifying SKIP_ZK environment configurations to resolve runtime inconsistencies and resolve execution failures during continuous integration.

How do I interpret Biome and TypeScript diagnostic outputs for Compact repositories?

Interpret Biome and TypeScript diagnostic outputs by reading the generated artifacts and source line numbers provided in the logs, which pinpoint formatting violations and type errors to apply targeted source fixes.

Why does my Vitest run fail after compiling Midnight contracts?

Vitest runs fail after compiling Midnight contracts when compact compiler outputs are stale or runtime versions mismatch; recompile contracts using the compact-compiler and verify Node version alignment before executing tests.

Can I use Playwright for end-to-end tests in a Midnight Compact project?

Playwright supports end-to-end testing in Midnight Compact projects, but requires proper browser installation and configuration to execute successfully alongside unit tests managed by Vitest.

When should I use the SKIP_ZK flag during Midnight CI runs?

Use the SKIP_ZK flag during Midnight CI runs to bypass zero-knowledge proof generation steps when troubleshooting compact compiler or runtime issues, allowing faster validation of contract compilation and test execution.