codestory-grounding

CodeStory Grounding

CodeStory helps an agent locate repository evidence, inspect source and follow relationships. The agent decides what to investigate and whether the evidence supports an answer. The skill does not expand the user's scope or authorize edits during a review.

Pass an absolute project root on every call. Keep project, source and publication identities attached when combining results across repositories.

Code-mode tools and results

Inspect selected tool declarations

When the needed operation is known, inspect its exact callable declaration. If you need an inventory first, print tool names, then inspect the declarations for the operations you choose. All operations remain available.

In hosts exposing ALL_TOOLS, a names-only inventory avoids printing every request and response schema:

text(ALL_TOOLS.filter(tool => /codestory/i.test(tool.name)).map(tool => tool.name));

After choosing an operation, match its actual exposed name exactly. This example selects search; choose any operation or set of operations the task needs:

const selectedNames = new Set(["mcp__codestory__search"]);
text(ALL_TOOLS.filter(tool => selectedNames.has(tool.name)));

Keep each selected declaration complete. Inspect further declarations when they become useful. A plugin-wide predicate over names and descriptions can print many unused declarations; discovery does not require displaying all of them. When a linked document path is already known, bound search to that file. Do not run a broad package or repository search merely to rediscover it.

Display each result payload once

Some hosts expose both content and structuredContent (or structured_content) to JavaScript. Printing the whole wrapper can put the same JSON payload into the model context twice.

Use one complete representation while retaining every other returned field. This example removes only plain text blocks that exactly match the serialized structured payload. Different spacing, key ordering or numeric spelling leaves the text in place; parsing it first could discard precision that only the text retains. Distinct text, annotations, images, resources, error flags and metadata stay intact. Keep the original result for programmatic use.