test

Sync the main branch, launch Docker services, and run build, lint, test, and e2e checks.

31|5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/NSEvteev/FullSpec --skill test-nsevteev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/test
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill test-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Final validation ensures the codebase is in a ready state by syncing the main branch, bringing up Docker services, and executing build, lint, unit, and end-to-end tests. It also generates a READY/NOT READY report to guide code review.

Core Features & Use Cases

  • Orchestrates end-to-end validation by coordinating version control sync, containerized services, and test suites.
  • Produces a concise readiness report to help engineers decide when to proceed with reviews.
  • Applicable after completing all TASK-N steps to guarantee a reproducible and verifiable readiness state.

Quick Start

Run the final validation after all TASK-N steps are completed.

Frequently Asked Questions about test

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

FAQPage Schema
How do I run end-to-end validation after syncing the main branch and launching Docker services?

End-to-end validation syncs the main branch, launches Docker services, and runs build, lint, unit, and e2e tests to generate a deterministic READY or NOT READY readiness report for code review.

What's the best way to automate a final readiness check across CI and local environments?

A final readiness check orchestrates version control sync, containerized Docker services, and test suites to produce a reproducible readiness state, ensuring verifiable completion criteria for both CI and local environments.

When do I need to execute end-to-end tests and generate a readiness report?

End-to-end tests and readiness reports are needed after completing all TASK-N development steps to guarantee a reproducible readiness state and guide engineers in deciding when to proceed with code reviews.

Does Docker need to be running to validate build, lint, and e2e test suites?

Docker services must be running to execute the final validation, as the process coordinates containerized services with build, lint, and e2e test suites to ensure a deterministic and reproducible readiness state.

Why does my final validation produce a NOT READY report instead of passing?

A NOT READY report indicates that build, lint, unit, or e2e test verifications failed during the final validation process, meaning the codebase does not meet the strict completion criteria required to proceed.

Can I use this final validation workflow for pre-review checks without a CI pipeline?

Yes, final validation applies to pre-review workflows and local environments by executing build, lint, and end-to-end tests independently, generating a concise readiness report to guide code review decisions.