# Repo Memory Skill Test Plan

## Purpose

This directory tracks human-readable test plans for the `skills/repo-memory/`
Codex skill bundle.

These documents are not direct CLI command-contract specs for `repo-memory`.
That coverage now lives under [../repo-memory/](../repo-memory/).

These documents are also not package-level unit tests for the runtime.
Those live under `packages/repo-memory-runtime/`.

This directory covers a different surface:

- whether an agent can actually use the packaged `repo-memory` skill
- whether the bundled `./assets/repo-memory` CLI works inside real skill-guided
  repository work
- whether durable repository knowledge is stored and retrieved correctly

## Test Model

- `README.md` is the index for this directory
- each skill test case lives in its own Markdown file
- use stable case slugs in filenames

## Shared Execution Contract

Use these defaults unless a case file explicitly overrides them:

- run the scenario with one real agent using the bundled `repo-memory` skill
- create an isolated temporary directory, repository fixture, and SQLite DB path
- require the agent to use the bundled `./assets/repo-memory` CLI instead of ad hoc
  notes
- validate final database state independently from the main thread after the
  agent stops

## Per-Case Template

Each case file should use this structure:

- `Test Type`
- `Purpose`
- `Preconditions`
- `Inputs`
- `Execution Parameters`
- `Execution Steps`
- `Validation Commands`
- `Expected Outcomes`
- `Assertions`
- `Cleanup`
- `Recorded Example Run` when a real run has already been captured

## Case Files

| Case Slug | File | Coverage Note |
| --- | --- | --- |
| `search-and-add-through-bundled-cli` | [search-and-add-through-bundled-cli.md](./search-and-add-through-bundled-cli.md) | validates that an agent can miss on search, add one durable entry, then retrieve it through the packaged `repo-memory` skill |

## Scope

In scope:

- explicit `$repo-memory` skill invocation
- bundled `./assets/repo-memory` CLI usage
- durable knowledge add/search/list/event flows
- package-backed SQLite memory database behavior as surfaced through the skill

Out of scope:

- direct CLI contract coverage that now belongs under [../repo-memory/](../repo-memory/)
- package-level unit tests for `packages/repo-memory-runtime`
- future auto-export flows such as `repo-brief` generation
- implicit skill triggering without `$repo-memory`