plan-local-codebase-chat
/plan-local-codebase-chat
How Ask Plan links a browser-selected local codebase and how to answer questions from its indexed snapshots instead of guessing from file names. Use when the user asks about their linked local codebase or `localCodebase` is in application state.
- Author
- builderio ↗
- Repository
- agent-native ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
How Ask Plan links a browser-selected local codebase and how to answer questions from its indexed snapshots instead of guessing from file names. Use when the user asks about their linked local codebase or `localCodebase` is in application state.
Original author description
How Ask Plan links a browser-selected local codebase and how to answer questions from its indexed snapshots instead of guessing from file names. Use when the user asks about their linked local codebase or `localCodebase` is in application state.
How it works
- Related Skills
SKILL.md preview
--- name: plan-local-codebase-chat description: >- How Ask Plan links a browser-selected local codebase and how to answer questions from its indexed snapshots instead of guessing from file names. Use when the user asks about their linked local codebase or `localCodebase` is in application state. --- # Local Codebase Chat The `local-codebase` application-state key is written by the Ask Plan browser folder picker when a user links a local codebase. It includes the selected folder name plus personal resource paths for the latest code index, file tree, and captured source snapshots. - The Ask Plan page can link a browser-selected local codebase folder. The UI indexes safe text files, skips generated/secret-looking paths, writes a small personal instruction resource under `instructions/local-codebases/`, and stores captured file snapshots under `codebases/<id>/snapshots/<timestamp>/`. - For live codebase questions, call `view-screen` when context is unclear and inspect `localCodebase`. First read its `indexPath` with the `resources` tool using `scope: "personal"`, then read relevant captured file `resourcePath`s before making claims. Do not infer API contracts, schema shape, or UI behavior from file names alone. - If the file needed to answer is absent or skipped, ask the user to sync again or attach the file instead of guessing. - For API/schema/UI visualization from a local codebase, call `get-plan-blocks` or `list-plan-components` before `visual-answer`, then publish blocks such as `openapi-spec`, `api-endpoint`, `data-model`, `diagram`, `file-tree`, `tabs`, and `annotated-code` grounded in the files you read. ## Related Skills - **visualize-repo** — durable repo-backed visual documentation from local plan MDX files. - **plan-source-sync** — reading and writing local plan folders.
Versions
The database has no other skills named plan-local-codebase-chat.
Database snapshot: 13.11.2026 · package version b0fd969b8dd0 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90understand-chat
Use when you need to ask questions about a codebase or understand code using a knowledge graph - 100understand-chat
Use when you need to ask questions about a codebase or understand code using a knowledge graph - 100local-doc-kb
Search the user's local document knowledge base (hybrid FTS + optional vectors, LLM file descriptions, OCR, media) built by local-doc-kb. Use when the user asks to find or answer from their own indexed folders / 本地知识库 / 本地文档. Not for web search. - 90codebase-questions
Answer questions about a repository indexed on repowise.dev with the Repowise tools. Use when the user asks what a repository contains, how its code works, where something is defined, how risky a change is, or about its code health, dead code or security findings. - 90codebase-exploration
Use when exploring, understanding, or answering questions about a Repowise-indexed codebase, including architecture, where code is implemented, how a module works, or which files are relevant before reading source. - 100docs-to-kg
Turn a product's docs (and the product itself, when you can read it) into a graph of its features written as user stories, in four snapshots: enumerated → merged → stories → linked. Use when someone wants to see what a product does, check docs against the product, or plan tests from them.