codestory-grounding

name	codestory-grounding
description	Use when an agent should ground a local repository with CodeStory before making source claims, planning edits, choosing tests, reviewing changes, or using broad retrieval evidence through the CodeStory plugin MCP.

CodeStory Grounding

CodeStory keeps a local repository map and broad-search index so agents can reach useful evidence without rediscovering the same code every turn.

The target is always the repository being grounded. Pass its exact absolute root as project on every CodeStory call. Never rely on a global active workspace.

Direct Tool Loop

Call the tool that matches the task. Do not call status first.

Using this skill does not require an MCP call when the requested work is fully local to an already named evidence surface—for example, inspecting or editing the content of assets/desk.svg. Inspect that surface directly. Naming a path does not make the evidence surface complete when the task asks about ownership, dependencies, runtime behavior, architecture, change impact, or another claim whose evidence extends beyond the file. For those tasks, select the narrowest CodeStory tool that can add evidence; do not call broad ground as a pre-edit ceremony.

1. Resolve the target repository root.
2. Call the intended tool with project=<absolute-root>.
3. If the result says state=preparing, wait for retry_after_ms and retry the same tool with the same arguments. The delay tracks observed preparation progress, so honor the reported value instead of a fixed poll interval. Do not poll status or ask the user to set up CodeStory.
4. Preserve cited anchors in source claims. Read focused source only for the remaining evidence gaps.

CodeStory prepares its local repository map and shared per-user retrieval server automatically. status and the project-bound codestory://status{?project} resource are optional diagnostics for a failed or unexpectedly slow request, not prerequisites for normal grounding.