midnight-cq:quality-init

Initializes Midnight Network code quality tooling with Biome, hooks, and CI workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Projects often suffer from inconsistent linting, formatting, missing CI checks, and scattered test scaffolding; this Skill standardizes and bootstraps a single, reproducible Biome-based code quality pipeline for Midnight Network projects to prevent tool drift and broken CI.

Core Features & Use Cases

  • Project detection: Detects Compact contracts, frontend DApps, existing Biome config, and conflicts like ESLint or Prettier.
  • Safe migration: Migrates ESLint and Prettier configs to Biome with guidance on limitations and manual follow-ups.
  • Scaffolding: Generates biome.json, .editorconfig, Husky pre-commit/pre-push hooks, and GitHub Actions workflows; conditionally adds Vitest for contract tests and Playwright for E2E.
  • CI and hooks strategy: Implements fast checks (checks.yml) and a separate test suite (test.yml) with path filtering, Compact compilation, type-checks, and conditional E2E jobs.

Quick Start

Run the quality-init flow to detect project type, migrate any ESLint/Prettier to Biome, and scaffold biome.json, Husky hooks, and CI workflows.

Frequently Asked Questions about midnight-cq:quality-init

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

FAQPage Schema
How do I migrate ESLint and Prettier to Biome for my project?

Yes, you can configure Husky hooks for Midnight Network projects by scaffolding pre-commit and pre-push hooks that enforce formatting and run fast checks before code is committed or pushed.

How do I set up GitHub Actions workflows with Vitest and Playwright?

Set up GitHub Actions by generating a checks.yml for fast checks and a test.yml for testing, using path filtering to conditionally trigger Vitest unit tests or Playwright E2E jobs based on project changes.

What is the best way to standardize linting and formatting across multiple projects?

Yes, the code quality setup supports both Compact contract projects and frontend DApps, detecting the project type to conditionally scaffold Vitest for contract tests and Playwright for E2E testing.

Why does my CI pipeline break from scattered test scaffolding and tool drift?

CI pipelines break due to inconsistent linting, formatting, and scattered test scaffolding; standardizing a Biome-based pipeline with automated GitHub Actions workflows prevents these broken CI states.

Can I use Biome instead of ESLint for linting a frontend DApp?

Yes, you can use Biome instead of ESLint for frontend DApps by migrating existing ESLint and Prettier configurations to Biome, creating a unified linting and formatting setup.