codemeridian-test-planning

CodeMeridian Test Planning Skill

Use this skill when working in a repository indexed by CodeMeridian and the user asks to add, update, review, or plan tests.

The goal is to identify the smallest useful set of tests before changing behavior or adding new code.

projectContext can be found in meridian.json in field project.

When To Use

Use this skill when the request includes words or intent like:

• add tests
• update tests
• fix failing tests
• what tests should I run
• what tests cover this
• improve coverage
• find missing tests
• test this feature
• test this bug fix
• validate this refactor
• behavior changed
• check regression risk
• make CI safer
• review test impact

Also use this skill before implementing behavior changes when test coverage is unclear.

Core Rule

Do not guess test coverage from filenames alone.

First identify:

1. the behavior being changed
2. the exact symbols or files involved
3. the tests already connected to that behavior
4. the gaps where no tests protect the behavior
5. the smallest test set that gives useful confidence

Workflow

1. Check Graph Freshness

When exact test relationships matter, check whether the graph matches the working tree.

Prefer:

• check_graph_freshness
• find_graph_drift

Report freshness clearly:

Graph freshness: fresh / stale / unknown

If freshness is stale or unknown, use graph results as guidance only and verify exact files manually.

2. Identify The Behavior Under Test

Clarify the behavior in implementation terms.

Prefer:

• analyze_feature_implementation_path when testing a feature request or docs/features/*.md
• build_minimal_context
• find_implementation_surface
• resolve_exact_symbol
• get_context_for_editing

Report:

Behavior under test:
- Feature / bug / refactor:
- Main symbols:
- Main files:
- Expected behavior:

If the behavior is unclear, state the assumption and continue with the safest likely interpretation.