test

Synchronize main branch, start docker services, run lint, build, and e2e tests, and report READY or NOT READY.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/oogDZ/2 --skill test-oogdz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/oogDZ/2/tree/main/.claude/skills/test
Command: npx skills add https://github.com/oogDZ/2 --skill test-oogdz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the final validation workflow to ensure code readiness by synchronizing with the main branch, starting services, and running tests, lint, and end-to-end checks, then reporting READY/NOT READY.

Core Features & Use Cases

  • Sync main branch state and boot required services via docker
  • Run make test, lint, build and end-to-end tests to verify completeness
  • Produce a readiness report indicating READY or NOT READY for code review

Quick Start

Run the /test command after all TASK-N tasks are completed to validate readiness for review.

Frequently Asked Questions about test

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

FAQPage Schema
How do I automate final validation for a code branch before review?

You automate final branch validation by synchronizing with the main branch, starting required docker services, and running lint, build, and e2e tests to produce a READY or NOT READY report.

What is the best way to run lint, build, and e2e tests in a CI pipeline?

Running lint, build, and e2e tests in a CI pipeline is best handled by an orchestration step that boots docker services, executes the test sequences, and generates a reproducible readiness report indicating review status.

Does this validation process support docker services and CI-CD workflows?

Yes, the final validation process supports CI-CD workflows by booting required docker services and synchronizing the main branch state before applying multi-step tests to verify code readiness for review.

How does branch readiness reporting work for end-to-end orchestration?

Branch readiness reporting works by applying end-to-end orchestration with robust error handling to execute make test, lint, build, and e2e checks, yielding a reproducible READY or NOT READY status report.

Why does my code branch need to sync with the main state before running e2e tests?

Your code branch needs to sync with the main state before running e2e tests to ensure the validation environment accurately reflects the target integration state and produces a reproducible readiness report.

What limitations exist when automating multi-step validation for docker services?

Limitations of automating multi-step validation for docker services include dependency on synchronized main branch state and the necessity of robust error handling to maintain reproducible reports across CI pipelines.