run-check-and-test

Run format, lint, type checks, tests, and builds from project manifests.

11|1|Updated Jun 7, 2025
One-click install
npx skills add https://github.com/baseballyama/eslint-plugin-postgresql --skill run-check-and-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-check-and-test
Source: https://github.com/baseballyama/eslint-plugin-postgresql/tree/main/.claude/skills/run-check-and-test
Command: npx skills add https://github.com/baseballyama/eslint-plugin-postgresql --skill run-check-and-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill automates the repository quality gate process by running the project's defined checks (format, lint, type checks, tests, and builds) so that changes can be validated before committing or opening a PR.

Core Features & Use Cases

  • Discover and run the project's quality gates by inspecting common manifests (package.json, Cargo.toml, pyproject.toml, Makefile) to locate the actual commands.
  • Execute checks in a deterministic sequence (format → lint → types → tests → build) and provide actionable failure guidance.
  • Use Case: After implementing changes, trigger the full check suite to confirm no regressions and maintain code health.

Quick Start

Run the project's full quality gates across the modified workspace and report any failures.

Frequently Asked Questions about run-check-and-test

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

FAQPage Schema
How do I run format, lint, type checks, tests, and builds before committing?

To run checks before committing, use this Skill to automatically discover and execute your project's quality gates by inspecting manifests like package.json or Cargo.toml. It runs format, lint, types, tests, and builds in a deterministic sequence, reporting failures with actionable guidance.

Can I run quality gates automatically across different programming languages?

Yes, you can run quality gates across different languages. The Skill inspects common manifests such as package.json, Cargo.toml, pyproject.toml, and Makefile to locate the actual commands, applying the verification sequence universally across your workspace.

What is the execution order for CI checks like format, lint, and tests?

The execution order for CI checks is a deterministic sequence: format runs first, followed by lint, then types, tests, and finally the build. This progression ensures code quality at each stage before advancing to heavier compilation.

Does this automation work with Makefile and pyproject.toml manifests?

Yes, this automation works with Makefile and pyproject.toml manifests. It also supports package.json and Cargo.toml, inspecting these files directly to find the declared scripts and execute the appropriate format, lint, type, test, and build commands.

How do I speed up iterative development when running local checks?

To speed up iterative development when running local checks, the Skill supports selective execution. Instead of running the entire suite, you can target specific quality gates, reducing validation time while maintaining code health.