full-knowledge-index

Indexes repository structure, architecture, and conventions into persistent agent memories.

10|1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/catalystctl/catcode --skill full-knowledge-index-catalystctl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: full-knowledge-index
Source: https://github.com/catalystctl/catcode/tree/main/.catalyst-code/skills/full-knowledge-index
Command: npx skills add https://github.com/catalystctl/catcode --skill full-knowledge-index-catalystctl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an AI agent first encounters a repository, it lacks durable knowledge of the codebase layout, build system, and conventions, forcing repeated re-exploration on every session. This Skill performs a structured full knowledge audit of a repository and persists the findings as reusable memories and skills. ## Core Features & Use Cases - Guided repository walk: Systematically traverses top-level directories, README anchors, manifests (Cargo.toml, go.mod, package.json), build scripts, and CI workflows to map subsystems and their interactions. - Memory reconciliation: Recalls existing workspace memories first, verifies them against disk, and appends or saves typed memories (architecture, convention, api, gotcha, build) without duplicating entries. - Skill gap detection: Lists existing skills and authors new SKILL.md files only for workflows solved two or more times, then reports memories touched and the area of least confidence. - Use Case: A developer onboarding an agent to a large Rust monorepo asks for a full knowledge index; the agent maps core/, tui/, sdk/, and web/ subsystems, saves build-test-release-flow memory, and finishes with a confidence report. ## Quick Start Run a full knowledge index of this repository to map its architecture, build flow, and conventions into persistent memories.

Frequently Asked Questions about full-knowledge-index

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I index a repository for an AI coding agent?

Run a full knowledge index that walks top-level directories, reads the README and manifests like Cargo.toml or package.json, maps subsystems, and saves findings as typed memories. This gives the agent durable context across sessions.

What is the difference between a full knowledge index and a codebase overview?

A codebase overview is a short orientation that does not persist anything, while a full knowledge index verifies facts against disk and saves durable architecture, build, and convention memories. Use the overview for quick questions and the index for lasting learning.

Does repository indexing duplicate existing memories?

No. The workflow recalls existing workspace memories first, treats them as hypotheses, verifies them against disk, and appends to existing entries rather than saving near-identical duplicates.

When should a new skill be created during repository indexing?

A new SKILL.md should only be written when a workflow has been solved two or more times and no existing skill covers it. One-off tasks should not become skills.

Why might indexed repository knowledge become outdated?

Module counts, dependency versions, and editor stacks drift as code changes. The index mitigates this by diffing memories against the actual directory listing and appending corrections instead of trusting stale documentation.