test
This slash command executes a test-driven development workflow through the agent-skills skill. Use it when building new features by writing failing tests first, then implementing code to pass them. For bug fixes, it employs the Prove-It pattern, requiring reproduction via a failing test before implementing and verifying the fix. Browser issues benefit from additional DevTools verification through the included integration.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/addyosmani/agent-skills/HEAD/.claude/commands/test.md -o ~/.claude/commands/test.mdtest.md
Invoke the agent-skills:test-driven-development skill. For new features: 1. Write tests that describe the expected behavior (they should FAIL) 2. Implement the code to make them pass 3. Refactor while keeping tests green For bug fixes (Prove-It pattern): 1. Write a test that reproduces the bug (must FAIL) 2. Confirm the test fails 3. Implement the fix 4. Confirm the test passes 5. Run the full test suite for regressions For browser-related issues, also invoke agent-skills:browser-testing-with-devtools to verify with Chrome DevTools MCP.
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
Simplify code for clarity and maintainability — reduce complexity without changing behavior