checkmate-init

Detect code quality tools and generate .claude/checkmate.json configurations.

5|3|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/rcrsr/checkmate --skill checkmate-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkmate-init
Source: https://github.com/rcrsr/checkmate/tree/main/skills/checkmate-init
Command: npx skills add https://github.com/rcrsr/checkmate --skill checkmate-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams automatically discover linting and formatting tools in a new project and generate a .claude/checkmate.json configuration, enabling immediate, consistent code-quality checks.

Core Features & Use Cases

  • Auto-detection of project structure to identify applicable tools (linters, formatters, and type checkers) across languages.
  • Auto-generation of a checkmate configuration that wires per-file-type checks with sensible defaults and excludes.
  • Use Case: Initialize code quality workflows for a fresh repository or monorepo, reducing setup time from hours to minutes.

Quick Start

Run /checkmate:init to start the guided setup and create .claude/checkmate.json based on your project.

Frequently Asked Questions about checkmate-init

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

FAQPage Schema
How do I auto-discover linting and formatting tools for a new project?

To auto-discover linting and formatting tools, run the guided setup to detect your project structure and generate a .claude/checkmate.json configuration with per-file-type checks and sensible defaults.

What is the best way to set up code quality checks in a monorepo?

Setting up code quality checks in a monorepo involves detecting applicable tools across multiple languages and environments, then generating a unified .claude/checkmate.json configuration file to wire per-file-type checks automatically.

How does checkmate config generation work for bootstrap linting pipelines?

Config generation works by performing environment detection and tool availability checks, then outputting a .claude/checkmate.json schema that maps formatting, linting, and type-checking pipelines with default exclusions.

Can I initialize type-checking workflows across different languages in a fresh repository?

Yes, you can initialize type-checking workflows across different languages in a fresh repository by auto-detecting the project structure to identify applicable type checkers and wiring them into the generated configuration.

Do I need to manually configure per-file-type checks when bootstrapping code quality?

No, you do not need to manually configure per-file-type checks because the tool auto-generates a checkmate configuration that wires these checks with sensible defaults and excludes based on your detected environment.

What are the limitations of auto-discovering code quality tooling?

The limitation of auto-discovering code quality tooling is that it relies entirely on environment detection and tool availability checks, meaning undiscovered or uninstalled linters and formatters will not be included in the generated configuration schema.