check

Run analyzer and tests via make check for pre-commit validation.

26|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Llloooggg/LetsFLUTssh --skill check-llloooggg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/Llloooggg/LetsFLUTssh/tree/main/.claude/skills/check
Command: npx skills add https://github.com/Llloooggg/LetsFLUTssh --skill check-llloooggg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run pre-commit validation by executing analyzer first and then tests, consolidating quality checks into a single step.

Core Features & Use Cases

  • Sequential validation: analyzer first, then tests
  • Quick feedback: concise results for passing or failing checks
  • CI-ready: integrates naturally into local development and CI pipelines

Quick Start

Run the full pre-commit validation by invoking make check to run the analyzer first, then the tests.

Frequently Asked Questions about check

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

FAQPage Schema
How do I run pre-commit code quality validation in one step?

Pre-commit validation is automated by running the analyzer first and then tests sequentially, consolidating quality checks into a single step. It produces a concise report indicating passing or failing checks.

What is the best way to automate code analysis and tests before committing?

Automating code analysis and tests is handled by invoking a single make check target, which runs the analyzer followed by tests to provide quick, consolidated feedback on code quality.

Does pre-commit validation work with existing CI pipelines?

Pre-commit validation integrates naturally into local development and CI pipelines, executing analysis and tests sequentially to validate changes before producing a concise pass or fail report.

Do I need make to run automated code quality checks?

Automated code quality checks require make with a defined make check target to perform analysis and tests sequentially, ensuring changes are validated during pre-commit or CI workflows.

What happens if code analysis fails during pre-commit validation?

Pre-commit validation runs the analyzer first and then tests sequentially, providing a concise report if checks fail to give quick feedback on code quality issues.

Can I use this for sequential validation of analyzer and tests?

Sequential validation executes the analyzer first and then tests, consolidating both quality checks into a single step to validate changes efficiently during pre-commit or CI workflows.