openlore-write-tests

openlore: Write Tests

When to use this skill

Trigger this skill when the user wants to write real tests for a function, module, or spec scenario, with phrasings like:

• "write tests for X"
• "add test coverage for Y"
• "what spec scenarios are untested?"
• "implement the test for this scenario"
• explicit command /openlore-write-tests

The rule: read the implementation and spec contract before writing a single assertion. No expect(true).toBe(true), no stubs, no placeholders.

Prerequisite: openlore analysis must exist (openlore analyze has been run). If orient returns "error": "no cache" → run openlore analyze first, then retry.

---

Step 1 — Identify target + detect framework

Ask the user:

1. Target — a function name, file path, spec scenario, or domain to test. If unsure, skip to Step 1b.
2. $PROJECT_ROOT — project root directory.

Step 1b — Find untested scenarios (if no target given)

Call the openlore MCP tool get_test_coverage with {"directory": "$PROJECT_ROOT"}.

Present the top 5 uncovered scenarios to the user, ranked by spec importance. Ask which to implement first.

Step 1c — Detect test framework

Scan the project root for framework config files:

File found	Framework
vitest.config.*, vitest.config.ts	Vitest — runner: npx vitest run <file>
jest.config.*	Jest — runner: npx jest <file>
pytest.ini, pyproject.toml (with [tool.pytest]), setup.cfg	pytest — runner: pytest <file> -v
CMakeLists.txt with enable_testing(), *.test.cpp	CTest/GTest — runner: build + ctest
go.mod	Go test — runner: go test ./...

Store as $TEST_RUNNER. If ambiguous, ask the user.

---

Step 2 — Orient

Call the openlore MCP tool orient with:

{
  "directory": "$PROJECT_ROOT",
  "task": "write tests for $TARGET",
  "limit": 5
}

Extract:

• $TARGET_FILE — the file containing the function(s) to test
• $EXISTING_TEST_FILE — nearby test file, if any (e.g. foo.test.ts, test_foo.py, foo_test.go)
• $SPEC_DOMAIN — the spec domain associated with the target