skills.rest
Tshah-95
Tshah-95COMMUNITY
Explore all skills by this author →
GitHub

testing

Run CLI-driven unit and E2E tests to verify AI orchestrator features.

Updated Jan 18, 2026
Search Tags:#testing#e2e#cli#verification#quality-assurance#unit-tests#integration-tests
One-click install
npx skills add https://github.com/Tshah-95/ai-orchestrator --skill testing-tshah-95
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/Tshah-95/ai-orchestrator/tree/main/.claude/skills/testing
Command: npx skills add https://github.com/Tshah-95/ai-orchestrator --skill testing-tshah-95

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that AI orchestrator changes are thoroughly validated through CLI runners, unit tests, and end-to-end tests to prevent regressions and guarantee maintainable code.

Core Features & Use Cases

  • CLI test runner for end-to-end verification
  • Unit and integration test coverage for all packages
  • E2E orchestration tests across orchestrator, agents, and UI

Quick Start

Run the CLI test runner to validate a feature end-to-end before shipping.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I run E2E tests for AI orchestrator features through a CLI runner?▼

Run E2E tests for AI orchestrator features by using a CLI test runner to validate end-to-end scenarios across agents and TUI. This enforces strict test execution requirements before shipping feature changes.

What is the best way to verify AI orchestrator changes and prevent regressions?▼

The best way to verify AI orchestrator changes is applying unit tests, integration tests, and E2E scenarios through a CLI runner. This validates features thoroughly to prevent regressions and guarantee maintainable code.

Do I need unit and integration test coverage for all packages when fixing bugs?▼

Yes, you need unit and integration test coverage for all packages when fixing bugs. The testing guidelines enforce strict test execution and documentation requirements across orchestrator, agents, and TUI changes.

Can I use CLI-driven tests for both feature development and UI changes?▼

Yes, you can use CLI-driven tests for feature development, bug fixes, and UI changes. The runner applies E2E orchestration tests across the orchestrator, agents, and TUI to verify changes.

Why does E2E testing fail without strict documentation and verification requirements?▼

E2E testing fails without strict documentation and verification because the project's testing guidelines enforce these requirements. Strict test execution ensures all orchestrator features are validated and maintainable.

Related Skills

Explore More Software Engineering Skills→
aws-samplesaws-samples
21

testing-strategy

Design test strategies for AI agents covering unit, integration, and memory tests.

Official
Advanced
DatTran26DatTran26

ck:test

Execute unit, integration, e2e, and UI tests with coverage reports.

Community
Advanced
nanorepublicananorepublica
61

Testing Test Writing

Enforce standardized test-writing guidelines within Claude Code workflows.

Community
Basic
adityaarsharmaadityaarsharma
2

orbit-qa-regression-pack

Manage regression test suites with Playwright and CI pipelines.

Community
Advanced