verify

Runs build, type check, lint, tests, security scan, and diff review with a structured pass/fail report.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/joydai2026-del/skills --skill verify-joydai2026-del
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/joydai2026-del/skills/tree/main/verify
Command: npx skills add https://github.com/joydai2026-del/skills --skill verify-joydai2026-del

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After implementing a feature or fix, it is easy to ship code that fails to build, breaks tests, leaks secrets, or contains leftover debug statements. This Skill runs a systematic 6-phase verification loop so nothing reaches a pull request unchecked. ## Core Features & Use Cases - 6-Phase Verification: Runs Build, Type Check, Lint, Test Suite, Security Scan, and Diff Review, each graded PASS, FAIL, WARN, or SKIP. - Auto-Detected Toolchains: Detects Flutter/Dart, Node.js, Rust, Go, and Python projects from manifest files and picks the right commands (npm test, cargo clippy, pytest, and more). - Security and Diff Checks: Greps changed files for leaked API keys and tokens, runs dependency audits, and flags debug statements, TODOs, merge conflict markers, and binary files. - Use Case: After finishing a feature branch in a Node.js project, invoke verification before opening the PR to confirm the build passes, all 47 tests pass with 82% coverage, no secrets are staged, and the diff is clean. ## Quick Start Ask the agent to run verification on the current project before creating the pull request.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I run all code quality checks before a pull request?▼

Invoke the verify skill after implementing changes. It auto-detects your project type and runs build, type check, lint, tests, security scan, and diff review, then outputs a structured report with a final PASS or FAIL verdict.

What checks should run before merging code?▼

At minimum run the build, type checker, linter, and test suite, plus a security scan for leaked secrets and dependency vulnerabilities. A diff review for debug statements, TODOs, and merge conflict markers catches issues tests miss.

Does the verification loop support Rust, Go, and Python projects?▼

Yes. It detects the project type from manifest files like Cargo.toml, go.mod, pyproject.toml, package.json, and pubspec.yaml, then runs the appropriate commands such as cargo clippy, go vet, ruff, pytest, or npm audit.

Can I run only a fast subset of the verification checks?▼

Yes. Quick mode runs only Build, Test, and Diff Review, skipping lint, type check, and security scan. It is intended for rapid iteration, while the full mode should gate the final pull request.

How does the security scan detect leaked API keys?▼

It greps staged and changed files for patterns like sk-, AKIA, ghp_, glpat-, private key headers, and token or password assignments. It also runs the project's dependency audit tool and fails on secrets or critical vulnerabilities.