verify
SolidActive QA verification - full validation before completion
AI & Automation 18 stars
5 forks Updated 2 days ago MIT
Install
Quality Score: 83/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
# Verify Mode
**Recommended model tier:** smart (opus) - this skill requires complex reasoning
Active QA verification: run all quality checks and report pass/fail status.
## Purpose
This is the VERIFY stage of the SDLC pipeline. Implementation is complete. Your job is to run comprehensive validation and report results.
**This is different from `review`**: Review is read-only analysis. Verify is active execution of quality checks.
## Verification Checklist
Run ALL of the following. Each must pass.
### 1. Full Test Suite
```bash
# TypeScript/JavaScript
npm test
# Go
go test ./...
# Python
pytest
```
**Expected**: All tests pass, no failures, no skipped tests.
### 2. Type Checking
```bash
# TypeScript
npx tsc --noEmit
# Go (implicit in build)
go build ./...
# Python (if using mypy)
mypy .
```
**Expected**: No type errors.
### 3. Linting
```bash
# TypeScript/JavaScript
npm run lint
# Go
go vet ./...
golangci-lint run
# Python
ruff check .
```
**Expected**: No lint errors. Warnings acceptable if pre-existing.
### 4. Build
```bash
# TypeScript/JavaScript
npm run build
# Go
go build ./...
# Python
python -m py_compile *.py
```
**Expected**: Build succeeds without errors.
### 5. Debug Artifact Check
Search for common debug artifacts that shouldn't be committed:
```bash
# Console logs (JS/TS)
Grep for "console.log" in changed files
# Debug prints (Go)
Grep for "fmt.Println" or "log.Print" that look like debug
# Python debug
Grep for "print(" or "pdb" or...
Details
- Author
- jmylchreest
- Repository
- jmylchreest/aide
- Created
- 7 months ago
- Last Updated
- 2 days ago
- Language
- Go
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
AI & Automation Listed
verify
Pre-merge verification gate. Build, test, and lint must all pass before marking done or shipping.
19 Updated yesterday
epicsagas Code & Development Listed
verify
Full verification loop - typecheck, test, lint, build. Use before committing or merging.
1 Updated 1 months ago
iamnolanhu AI & Automation Listed
qa
Use after finishing a feature or fix to confirm it actually works, when the user says "test this", "does it work", "verify this", "QA it", or before shipping something that has never been driven end-to-end. Also when the user asks for tests to be written or wants to work test-first.
23 Updated today
mehrad-dm