Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
Runs comprehensive codebase verification including build, types, lint, tests, console.log audit, and git status. Produces PASS/FAIL report. Supports quick, full, pre-commit, pre-pr modes.
npx claudepluginhub divenhuang88/everything-claude-codeHow this command is triggered — by the user, by Claude, or both
Slash command
/everything-claude-code:verifyThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Verification Command Run comprehensive verification on current codebase state. ## Instructions Execute verification in this exact order: 1. **Build Check** - Run the build command for this project - If it fails, report errors and STOP 2. **Type Check** - Run TypeScript/type checker - Report all errors with file:line 3. **Lint Check** - Run linter - Report warnings and errors 4. **Test Suite** - Run all tests - Report pass/fail count - Report coverage percentage 5. **Console.log Audit** - Search for console.log in source files - Report locations 6....
/verifyRuns comprehensive codebase verification including build, types, lint, tests, console.log audit, and git status. Produces PASS/FAIL report. Supports quick, full, pre-commit, pre-pr modes.
/verifyRuns verification checks on codebase including types (mypy), lint (ruff), tests (pytest cov), security (pip-audit), secrets, prints, and git status. Outputs summary report with pass/fail and readiness status.
/verifyRuns full verification pipeline: build, type check, lint, tests, security scan, git status. Outputs structured phased PASS/FAIL report with next steps.
/fire-double-checkVerifies work completion claims by running npm build, test, typecheck, and lint checks on current work or specified target, reporting results with evidence and exit codes.
/verifyVerifies code changes before completion claims by auto-detecting stack, running tests/lints/type-checks/builds, and providing checklists with actual outputs.
/verifyVerifies all git-changed files for common mistakes, logic errors, and security issues, outputting per-file summaries with issue counts and severity ratings (CRITICAL, WARNING, INFO).
Share bugs, ideas, or general feedback.
Run comprehensive verification on current codebase state.
Execute verification in this exact order:
Build Check
Type Check
Lint Check
Test Suite
Console.log Audit
Git Status
Produce a concise verification report:
VERIFICATION: [PASS/FAIL]
Build: [OK/FAIL]
Types: [OK/X errors]
Lint: [OK/X issues]
Tests: [X/Y passed, Z% coverage]
Secrets: [OK/X found]
Logs: [OK/X console.logs]
Ready for PR: [YES/NO]
If any critical issues, list them with fix suggestions.
$ARGUMENTS can be:
quick - Only build + typesfull - All checks (default)pre-commit - Checks relevant for commitspre-pr - Full checks plus security scan