Repository Intelligence Recipe

Use repo-intelligence when the first job is mapping codebases, owners, stacks, status, and evidence trails.

Generate

node generator/create-index.mjs \
  --name "Platform Repo Index" \
  --slug platform-repo-index \
  --output ./platform-repo-index \
  --profile repo-intelligence \
  --owner "Platform Engineering" \
  --services github,linear \
  --skip-install

What Gets Generated

• docs/ for investigation notes and public workspace guidance.
• repos/index.yaml for tracked repositories.
• workspaces/ metadata for structured repo investigations.
• mcp/ TypeScript MCP starter files for read-only repository context.

First Validation

cd platform-repo-index
npm install
npm run mcp:check
npm run docs:build

Next Steps

• Add each repository with owner, status, stack, purpose, tags, and start-here files.
• Prefer concrete source paths over broad summaries.
• Keep stale or archived repos in the registry only when they still affect active decisions.
• Use MCP search once the registry has enough evidence to help agents choose a starting point.

See MCP Context for the read-only resource and tool model.