verify

Name: verify
Availability: InStock
Author: RediSearch

Run formatting, linting, building, and tests before commits or PRs.

6.2k|590|Updated May 5, 2016

Search Tags:#build #pre-commit #verify #lint #format #tests

Ready to run

npx skills add https://github.com/RediSearch/RediSearch --skill verify-redisearch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/RediSearch/RediSearch/tree/main/.skills/verify
Command: npx skills add https://github.com/RediSearch/RediSearch --skill verify-redisearch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the verification workflow to prevent faulty code from entering main branches, reducing rework and review time.

Core Features & Use Cases

Enforces code quality by running formatting, linting, building, and tests before commits or PRs.
Applies a repeatable, language-agnostic verification process across projects to speed up reviews.
Use Case: prior to merging a feature, run the checks locally to guarantee that the codebase builds and passes tests.

Quick Start

Run the following checks in order:

make fmt CHECK=1
make lint
./build.sh
Run tests (adjust to your language/tooling, e.g., cargo nextest run or npm test)

Frequently Asked Questions about verify

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

FAQPage Schema

How do I prevent faulty code from entering my main branch?▼

Automate code verification by running formatting, linting, building, and tests before commits or PRs. This Skill enforces these checks locally using standard tools, ensuring deterministic results and preventing broken code from merging.

Can I run pre-commit verification across different programming languages?▼

Yes, this verification process is language-agnostic. It applies a repeatable workflow across projects by running standard tools like fmt, lint, build scripts, and test suites appropriate to each language.

What checks should I run before submitting a pull request?▼

Run formatting, linting, building, and tests in order: apply code formatting checks, run linters, execute build scripts, then run your language-specific test suite to guarantee the codebase builds and passes all tests.

How does pre-commit verification speed up code review?▼

By enforcing formatting, linting, building, and tests locally before submission, you eliminate review delays caused by style issues, missing dependencies, or test failures, reducing rework and review time.

Do I need special tools to verify code before commits?▼

No. This Skill uses standard, existing tools in your tech stack—fmt and lint tools, build scripts, and test suites you already have. No additional dependencies are required.

What happens if verification fails before a commit?▼

The verification process halts and reports which checks failed—formatting, linting, build, or tests. Fix the issues locally and re-run verification until all checks pass before committing or opening a PR.