Skill Claude CodeCodex
Identify and write E2E tests for the most critical user flows (top 3–5) that impact revenue or retention. Use when defining smoke tests or deciding what to test first.
Skill Claude CodeCodex
Identify and write E2E tests for the most critical user flows (top 3–5) that impact revenue or retention. Use when defining smoke tests or deciding what to test first.
Skill Claude CodeCodex
Write tests for error paths, including exceptions, rejected promises, fallback behavior, and invalid inputs. Use when the user wants to cover failure modes, edge cases, or “unhappy paths.”.
Skill Claude CodeCodex
Create reusable mock or stub factories that generate configurable, typed fakes for tests. Use when mocks are repetitive, hard to maintain, or need per-test customization.
Skill Claude CodeCodex
Test that users cannot access others’ resources, covering IDOR, role violations, and ownership checks. Use when validating authorization, access control, or multi-tenant isolation.
Skill Claude CodeCodex
Write tests for background jobs and queue workers covering processing logic, retries, and failure handling. Use when testing workers, job processors, or queue consumers and their behavior.
Skill Claude CodeCodex
Create typed fixture and factory systems for test data with sensible defaults and per-test overrides. Use when tests repeat large objects or need reusable data builders.
Skill Claude CodeCodex
Fix test isolation by removing shared state, global side effects, and order dependencies. Use when tests are flaky, fail in CI, or pass individually but fail together.
Skill Claude CodeCodex
Write tests for third-party integrations using mocks, fixtures, or sandboxes to verify API calls, webhooks, retries, and failure handling without hitting live services.
Skill Claude CodeCodex
Generate unit tests covering happy paths, edge cases, boundaries, and error conditions with meaningful assertions. Use when the user asks to write tests, improve coverage, or verify behavior of a function or module.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: