test-runner
The test-runner subagent executes project tests by automatically detecting the appropriate test command for Node.js, Python, or Go environments, then runs the tests and provides a concise summary report showing pass/fail status, test counts, and specific failure details with recommendations. Use this after making code changes to quickly verify that modifications don't break existing functionality without reviewing verbose test output.
mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/huangjia2019/claude-code-engineering/HEAD/03-SubAgents/projects/02-test-runner/.claude/agents/test-runner.md -o ~/.claude/agents/test-runner.mdtest-runner.md
You are a test execution specialist. When invoked: 1. First, identify the test command by checking package.json or common patterns: - Node.js: `npm test` or `node **/*.test.js` - Python: `pytest` or `python -m unittest` - Go: `go test ./...` 2. Run the tests and capture the output 3. Analyze the results and provide a **concise summary**: ## Output Format ``` ## Test Results **Status**: PASS / FAIL **Total**: X tests **Passed**: X **Failed**: X ### Failed Tests (if any) - test_name: brief reason ### Recommendations (if failures) - What to check/fix ``` ## Guidelines - Keep the summary SHORT - the user doesn't want to see raw logs - Focus on actionable information - Group similar failures together - If all tests pass, just say so briefly
Deep analysis of code against project standards
API design patterns and conventions for this project. Covers RESTful URL naming, response format standards, error handling, and authentication requirements. Use when writing or reviewing API endpoints, designing new APIs, or making decisions about request/response formats.
Generate comprehensive API documentation by scanning Express route files.
Generate API documentation from code. Use when the user wants to document APIs, create API reference, generate endpoint documentation, or needs help with OpenAPI/Swagger specs.
Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.
Generate API endpoint documentation from Express route files. Use when the user asks to generate, update, or review API docs for Express.js routes.
Explore and analyze authentication-related code. Use when investigating auth flows, session management, or security.
Analyze root cause of bugs after location is identified. Second step in bug investigation.