changelog-observer
Track development session events in a daily markdown changelog, including file changes, test results, and key decisions.
Test execution reference: framework detection (pytest/jest/vitest/go/cargo/junit) and correct run/coverage commands, plus failure-analysis steps. Use when running tests, analyzing test failures, or verifying coverage after code changes.
$ npx -y skills add claude-world/director-mode-lite --skill test-runner --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/test-runnerContext preview
The summary Claude sees to decide when to auto-load this skill.
Test execution reference: framework detection (pytest/jest/vitest/go/cargo/junit) and correct run/coverage commands, plus failure-analysis steps. Use when running tests, analyzing test failures, or verifying coverage after code changes.
name: test-runner description: "Test execution reference: framework detection (pytest/jest/vitest/go/cargo/junit) and correct run/coverage commands, plus failure-analysis steps. Use when running tests, analyzing test failures, or verifying coverage after code changes." user-invocable: false
> **Director Mode Lite** - Test Execution Reference
---
Detect the project's test framework, then use its runner:
| Language | Frameworks | |----------|------------| | JavaScript/TypeScript | Jest, Vitest, Mocha, Playwright | | Python | pytest, unittest | | Go | go test | | Rust | cargo test | | Java | JUnit, Maven, Gradle |
Check for configuration files:
Run tests with the detected framework's command:
# JavaScript/TypeScript npm test # or pnpm test / yarn test # Python pytest -v # Go go test ./... # Rust cargo test
For coverage, add the framework's coverage flag (for example `pytest --cov`, `jest --coverage`, `go test -cover ./...`, `cargo tarpaulin`).
For each failure, capture: 1. **Test name** and file location 2. **Expected** vs **Actual** result 3. **Root cause** analysis 4. **Suggested fix**
## Test Results **Status**: 2 failed, 18 passed (90% pass rate) ### Failed Tests #### 1. `user.test.ts` - should validate email format - **Location**: `src/tests/user.test.ts:45` - **Expected**: `false` for invalid email - **Actual**: `true` - **Root Cause**: Regex pattern missing check for domain - **Fix**: Update regex in `validateEmail()` function #### 2. `api.test.ts` - should return 401 for unauthorized - **Location**: `src/tests/api.test.ts:78` - **Expected**: Status 401 - **Actual**: Status 500 - **Root Cause**: Auth middleware throwing unhandled error - **Fix**: Add try-catch in auth middleware ### Coverage Summary - Statements: 85% - Branches: 72% - Functions: 90% - Lines: 84%
When working with the `/test-first` command:
1. **Red**: Write a failing test first 2. **Green**: Implement the minimum code to pass 3. **Refactor**: Improve without changing behavior
Cycle: Write Test → Run (Fail) → Implement → Run (Pass) → Refactor → Run (Pass)
Use Claude Code like a Director, not a Programmer. MIT toolkit with Auto-Loop, guided setup, 27 commands, 14 agents, and 32 skills.
Track development session events in a daily markdown changelog, including file changes, test results, and key decisions.
Validate custom agent file format and structure. Use after creating or editing an agent, before committing agent changes, or when an agent fails to load.
Generate custom agent from template. Use when creating a new subagent from scratch, or scaffolding an agent file with correct frontmatter.
List all available agents (core, expert, self-evolving). Use when the user asks what agents are available or runs /agents.
TDD-based autonomous development loop with checkpoint recovery and observability changelog