test
Comprehensive testing workflow - unit tests ∥ integration tests → E2E tests
npx skills add parcadei/Continuous-Claude-v3 --skill test --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /test - Testing Workflow Run comprehensive test suite with parallel execution. ## When to Use - "Run all tests" - "Test the feature" - "Verify everything works" - "Full test suite" - Before releases or merges - After major changes ## Workflow Overview ``` ┌─────────────┐ ┌───────────┐ │ diagnostics │ ──▶ │ arbiter │ ─┐ │ (type check)│ │ (unit) │ │ └─────────────┘ └───────────┘ │ ├──▶ ┌─────────┐ ┌───────────┐ │ │ atlas │ │ arbiter │ ─┘ │ (e2e) │ │ (integ) │ └─────────┘ └───────────┘ Pre-flight Parallel Sequential (~1 second) fast tests slow tests ``` ## Agent Sequence | # | Agent | Role | Execution | |---|-------|------|-----------| | 1 | **arbiter** | Unit tests, type checks, linting | Parallel | | 1 | **arbiter** | Integration tests | Parallel | | 2 | **atlas** | E2E/acceptance tests | After 1 passes | ## Why This Order? 1. **Fast feedback**: Unit tests fail fast 2. **Parallel efficiency**: No dependency between unit and integration 3. **E2E gating**: Only run slow E2E tests if faster tests pass ## Execution ### Phase 0: Pre-flight Diagnostics (NEW) Before running tests, check for type errors - they often cause test failures: ```bash tldr diagnostics . --project --format text 2
- When to Use
- Workflow Overview
- Agent Sequence
- Why This Order?
- Execution
- Phase 0: Pre-flight Diagnostics (NEW)
- Phase 0.5: Change Impact (Optional)
- Phase 1: Parallel Tests
- Phase 2: E2E Tests (If Phase 1 Passes)
- Test Scopes
- Full Suite
- Feature Scope
- Quick Check
- Example
tldr diagnostics . --project --format text 2>/dev/null | grep "^E " | head -10 tldr change-impact --session or for explicit files: tldr change-impact src/changed_file.py
What does the test skill do?
Comprehensive testing workflow - unit tests ∥ integration tests → E2E tests
How do I install it?
Run `npx skills add parcadei/Continuous-Claude-v3 --skill test --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From parcadei/Continuous-Claude-v3, a repository with 3,879 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.