verify

Automates a 6-phase code verification loop: build, lint, test, security scan, diff review.

14|2|Updated Jan 28, 2026

Search Tags:#code quality #testing #linting #verification #security scan #pr-ready

Ready to run

npx skills add https://github.com/excatt/superclaude-plusplus --skill verify-excatt

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the rigorous verification of code quality, ensuring that code is buildable, type-safe, linted, tested, secure, and ready for review before it's committed or submitted as a Pull Request.

Core Features & Use Cases

Comprehensive Checks: Executes a 6-phase pipeline including build, type checking, linting, testing, security scanning, and diff review.
Configurable Modes: Offers different verification levels (Quick, Full, Pre-PR, Pre-Commit) to suit various stages of the development workflow.
Use Case: Before submitting a Pull Request for a new feature, run /verify pre-pr to catch potential issues early, reducing review time and preventing bugs.

Quick Start

Run the full verification process on your current code changes.

Frequently Asked Questions about verify

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

FAQPage Schema

How do I automate code quality checks before submitting a pull request?▼

Automated code quality checks before a pull request require a systematic verification loop covering build success, type safety, linting compliance, test coverage, security scanning, and diff review. This 6-phase pipeline catches potential issues early, reducing review time and preventing bugs.

What is a pre-PR verification pipeline and when do I need to run one?▼

A pre-PR verification pipeline validates build success, type safety, linting compliance, test coverage, security vulnerabilities, and diff review. Run this 6-phase process post-implementation, post-refactoring, or before submitting a Pull Request to ensure code quality and review readiness.

Can I run a quick code linting and type safety check without executing the full test suite?▼

Quick verification modes allow you to run linting and type safety checks without executing the full test suite. Configurable levels like Quick, Full, Pre-PR, and Pre-Commit suit various stages of the development workflow without requiring a complete 6-phase pipeline every time.

Does automated security scanning catch vulnerabilities during the code verification process?▼

Automated security scanning is a core phase of the code verification process, detecting vulnerabilities before code is committed. The pipeline includes security vulnerability detection alongside build, type checking, linting, testing, and diff review to ensure comprehensive quality assurance.

What is the best way to ensure type safety and linting compliance after a major code refactoring?▼

The best way to ensure type safety and linting compliance post-refactoring is a systematic 6-phase verification loop. This automated pipeline validates build success, type checking, linting rules, test coverage, and security scans to guarantee the refactored code remains stable and pr-ready.

Why does my code pass local linting but fail the pre-commit verification pipeline?▼

Local linting may pass but pre-commit verification pipelines fail when broader checks like build success, type safety, test coverage, or security vulnerability detection are triggered. The 6-phase process enforces comprehensive quality compliance beyond basic linting rules before allowing a commit.