This repo is indexed by graft/. For ANY task here, whether understanding how something works, finding where code lives, tracing what calls a symbol or what a change breaks, or scoping an edit, get your context from graft before grepping or reading source files.
This skill should be used when understanding code structure, finding dependencies between functions/classes, tracing call graphs, or exploring code relationships. Trigger phrases include 'code graph', 'call graph', 'who calls', 'what calls', 'find dependencies', 'code structure', 'inheritance', 'find paths'.
This skill enables deep semantic and structural analysis of C/C++ codebases using a pre-built Neo4j GraphRAG. It provides insights into call chains, class hierarchies, macro causality, and type aliases.
Use for TypeScript/JavaScript codebase navigation — symbol lookup, blast radius, reuse checks, and repo orientation. Prefer agentmap before serial grep when exploring imports, exports, or where a symbol lives. Package is @raymondchins/agentmap (not the unrelated npm package agentmap).
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.
Trustworthy, code-grounded repo memory for coding agents. Before any task, recall grounded repo knowledge (decisions, bugs, conventions, code paths); after learning something durable, capture it; never act on stale or hallucinated memory. Use at the start of every task, when debugging, and after solving something…
Use when investigating a repository, searching for implementation, reviewing changes, working from specs/docs, or preparing a risky code change in an environment where m1nd is available. This doctrine makes m1nd the first investigative layer before grep, glob, or manual file reads, except when the task is pure…
Use when continuing, coordinating, reviewing, or handing off the M1ND-10 program; protecting its candidate tree; advancing G0-G10; freezing or releasing a candidate; activating autonomy; or when the user asks an agent to act as M1ND guardian. Enforces one-active-front execution, proof-state separation, same-candidate…
Use when the user mentions m1nd or when repo investigation, search, review, docs/spec work, or risky change prep should go through m1nd first before grep, glob, or manual file reads. Covers m1nd-first routing, L1GHT and universal document ingestion, risky edit preparation, document-to-code binding, the served owner +…
Prepare a release of ragforgit — write human-readable Russian release notes into CHANGELOG.md, bump the version and rebuild plugin manifests. Use when the user asks to cut a release, bump the version, or prepare a dev → main merge ("подготовь релиз", "выпусти версию", "бампни версию", "release notes").
Use when configuring or changing a repository's tracked branches, layered review policy, ignored tracked paths, retrieval limits, summary depth, or non-secret task-board metadata.
Propose a new change with all artifacts generated in one step. Use when the user wants to describe what they want to build and get a complete proposal with specs and tasks ready for implementation.
Navigates the local RepoSkein Code Property Graph to understand repository architecture. Use whenever modifying code, tracing dependencies, assessing change impact, or summarizing functions in a repo containing .reposkein/.
Installs and verifies RepoSkein (the deterministic code-graph MCP server) in the current repository. Use when an agent wants RepoSkein's structural navigation but the tools are missing, error with "REPOSKEINREPOPATH", or the repo has no .reposkein/ directory — i.e. set RepoSkein up and confirm it runs.
How a new language enters Kivgraph's graph - the two routes and why one of them is almost always wrong, the four decisions that cannot be migrated later, the branches that decide what your language is without asking, and the gates that fail closed. Use when adding or extending language support, when touching…
Cómo y sobre todo cuándo se publica una release de Kivgraph - la versión sólo sube, los tres sitios donde vive, qué verifica CI, y la lista de cambios que NO merecen release. Usar al proponer o preparar una release, al tocar internal/version/version.go, al crear un tag vX.Y.Z, o cuando alguien pida "saca una versión".
Cómo se ejecutan y se escriben los tests de Kivgraph - las tres suites, el tag ladybug que no se invoca a mano, qué se salta y por qué, y el smoke test del binario. Usar al correr tests, al añadirlos, ante un fallo de enlazado library 'lbug' not found, ante un SKIP inesperado, o antes de cerrar una tarea.
Audit a PR's structural choices against architecture-priming, the repo's own architecture.md, and any nested boundary configs. Use when the user says "audit this PR's architecture", "check the boundaries", "is this PR clean structurally", "post-merge review of.
Voice, tone, and format for the public Codemap docs (apps/docs, built with Blume). Use when authoring or editing apps/docs prose — landing, guides, concepts, recipes, reference, generated API — or deciding headline grammar, benefit framing, peer framing, or anti-pitch wording.