skills.rest
stevenandteresa-maker
stevenandteresa-makerCOMMUNITY
Explore all skills by this author →
GitHub

everystack-verify

Automate EveryStack build verification with typechecking, linting, tests, and coverage analysis.

Updated Aug 27, 2026
Search Tags:#code quality#testing#verification#coverage#build process#ci
One-click install
npx skills add https://github.com/stevenandteresa-maker/EveryStack --skill everystack-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: everystack-verify
Source: https://github.com/stevenandteresa-maker/EveryStack/tree/main/docs/skills/verify
Command: npx skills add https://github.com/stevenandteresa-maker/EveryStack --skill everystack-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a comprehensive and standardized process for verifying EveryStack builds, ensuring code quality, test coverage, and build integrity before deployment.

Core Features & Use Cases

  • Full Verification Suite: Executes typechecking, linting, i18n checks, unit tests, integration tests, and coverage analysis in a defined sequence.
  • Failure Mode Guidance: Offers specific solutions for common errors like connection issues, tenant isolation failures, and migration problems.
  • Use Case: After a new feature is built, use this Skill in a dedicated VERIFY context to run the entire test suite, identify any regressions, and fix them before merging.

Quick Start

Use the everystack-verify skill to run the full verification suite for the latest build.

Frequently Asked Questions about everystack-verify

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

FAQPage Schema
How do I automate build verification for typechecking, linting, and unit tests?▼

Automate build verification by running a full suite that executes typechecking, linting, i18n checks, unit tests, integration tests, and coverage analysis in a defined sequence to ensure code quality.

What is a BUILD and VERIFY context separation for running CI tests?▼

A BUILD and VERIFY context separation isolates the test verification process from the build process, which is required for optimal performance when running comprehensive coverage analysis and integration tests.

How do I enforce code coverage thresholds during the build process?▼

Enforce code coverage thresholds by running an automated verification suite that includes coverage analysis, preventing deployments that do not meet the required test coverage metrics for your build.

Why does my integration test fail with tenant isolation or connection issues?▼

Tenant isolation or connection issues during integration tests are common failure modes that can be resolved using specific guidance provided by the automated verification suite during the test run.

Can I run i18n checks alongside unit and integration tests in CI?▼

Yes, you can run i18n checks alongside unit and integration tests because the automated verification process executes all these checks in a defined sequence within a dedicated verify context.

How do I fix migration problems found during build verification?▼

Fix migration problems detected during build verification by following the specific failure mode guidance provided for common errors, ensuring database integrity before merging new features.

Related Skills

Explore More Software Engineering Skills→
dislerdisler
379

Agent Sandboxes

Execute isolated code and tasks inside E2B sandboxes.

Community
Advanced
DenissvgnDenissvgn

merge-agent

Automate authorized feature branch merges into main with validation and rollback.

Community
Basic
imkdwimkdw
1

Backend Migrations

Automate Prisma migrations for PostgreSQL schema changes.

Community
Intermediate
a29paula29paul
1

health

Aggregate type checker, linter, test runner, and dead code detector results into a weighted 0-10 code quality score.

Community
Advanced