test-and-verify

Run format, lint, type check, and tests as quality gates.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/MichielDean/LLMem --skill test-and-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-and-verify
Source: https://github.com/MichielDean/LLMem/tree/main/skills/test-and-verify
Command: npx skills add https://github.com/MichielDean/LLMem --skill test-and-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discover how to keep code healthy by automatically running a structured set of quality gates (format, lint, typecheck, and tests) before code changes are merged, preventing regressions and shipping issues.

Core Features & Use Cases

  • Runs a deterministic suite of quality gates across common languages to validate code health.
  • Applies to local development, PR validations, and CI pre-checks to ensure consistent standards.
  • Use Case: A developer updates a module and uses this Skill to confirm formatting, static types, and tests pass before pushing.

Quick Start

Run the configured quality gates on your local changes before committing.

Frequently Asked Questions about test-and-verify

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

FAQPage Schema
How do I automate quality gates to prevent broken code from shipping?

Automate quality gates by running a stepwise pipeline that validates format, lint, type checks, and tests before merging code. This process prevents regressions and ensures readiness for commits, PRs, and CI by logging outcomes for auditing.

What are quality gates in CI and local development workflows?

Quality gates in CI and local workflows are deterministic validation steps that confirm code health. They apply format, lint, typecheck, and test checks to ensure consistent standards across local development, PR validations, and CI pre-checks.

How do I run lint, format, and type checks before pushing a commit?

Run lint, format, and type checks before pushing by executing a configured stepwise pipeline on your local changes. This validates formatting, static types, and tests, confirming code readiness and preventing shipping issues before you commit.

Can I use this quality gate pipeline for PR validations and CI pre-checks?

Yes, you can use this quality gate pipeline for PR validations and CI pre-checks. It applies consistent standards across any repository by validating format, lint, type checks, and tests to ensure code health before changes are merged.

What is the best way to validate code health before merging a pull request?

The best way to validate code health before merging a PR is to run a structured suite of quality gates. This deterministic pipeline checks formatting, static types, and tests, preventing regressions and ensuring consistent standards.

Are the quality gate commands configurable for different repositories?

Yes, the quality gate commands are configurable. The stepwise pipeline runs format, lint, type check, and tests with configurable commands, allowing adaptation for any repository while logging outcomes for auditing.