verify

Run tests, type checks, linting, and builds across TypeScript, Go, and Python.

15|4|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/jmylchreest/aide --skill verify-jmylchreest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/jmylchreest/aide/tree/main/skills/verify
Command: npx skills add https://github.com/jmylchreest/aide --skill verify-jmylchreest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Active QA verification ensures comprehensive validation before release by running a complete suite of checks.

Core Features & Use Cases

  • Runs tests across TypeScript/JavaScript, Go, and Python.
  • Performs type checking, linting, and builds.
  • Generates a verification report highlighting pass/fail status.

Quick Start

Trigger the verify skill to run the full verification workflow and review the results.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I run end-to-end QA verification across TypeScript, Go, and Python projects?

End-to-end QA verification runs tests, type checks, linting, and build steps across TypeScript/JavaScript, Go, and Python projects to validate code before release. It executes commands like npm test, go test ./..., and python -m py_compile to ensure comprehensive checks.

What does automated type checking and linting include for a multi-language codebase?

Automated type checking and linting for a multi-language codebase includes running npx tsc --noEmit for TypeScript, golangci-lint run and go vet ./... for Go, and scanning for debug artifacts to validate code quality before release.

Can I use a single workflow to run tests, lint, and build steps before release?

Yes, you can use a single workflow to run tests, lint, and build steps before release. The verification process executes npm test, npx tsc --noEmit, go test ./..., and golangci-lint run across supported languages to generate a pass/fail report.

What is the best way to automate pre-release quality checks for Go and Python?

The best way to automate pre-release quality checks for Go and Python is to run a verification workflow that executes go test ./..., go vet ./..., golangci-lint run, and python -m py_compile *.py to validate code and generate a verification report.

Does the verification workflow scan for debug artifacts during the build process?

Yes, the verification workflow scans for debug artifacts during the build process. This debug artifact scan is integrated alongside type checks, linting, and tests to ensure no leftover debugging code reaches release.

Why does my CI pipeline need a dedicated verification stage before deployment?

A CI pipeline needs a dedicated verification stage to validate code before release by running a complete suite of checks including tests, type checking, linting, and builds. This ensures comprehensive quality validation and generates a pass/fail report.