From mantis
Index a local codebase into a CSV for Mantis, optionally creating and activating a Mantis codebase map. Use when the user wants Claude Code to map a repository or create a codebase CSV.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mantis:codebaseThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use `mantis create codebase`. This command is local-first: it scans files on the user's machine and writes a CSV. It can optionally continue into `mantis create map`.
Use mantis create codebase. This command is local-first: it scans files on the user's machine and writes a CSV. It can optionally continue into mantis create map.
$ARGUMENTS or ask the user.mantis create codebase "./repo" --out "./repo-codebase.csv"
path: repo-relative file pathfile_nameextensionlanguagekind: rough file role such as component, route, api, utility, test, sourcelocbytesimportssummarycontentIf the user wants the codebase to become a Mantis map immediately, run:
mantis create codebase "./repo" \
--create-map \
--space-mode new \
--space-name "Codebase: Repo Name" \
--private \
--map-name "Source Code Index" \
--activate \
--thread-name "Architecture Review"
The command uses good defaults for codebase maps:
title: pathsemantic: summary,content,importscategoric: language,kind,extensionnumeric: loc,bytesIf --activate was used, tell the user to run:
/reload-plugins
Then suggest prompts like:
What are the main architectural zones in this codebase?
Which files are central or risky?
Where should I start if I want to refactor the map rendering system?
mantis setup first if API configuration is missing..git, node_modules, .next, dist, build, and caches.Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub kellislab/mantis-cli --plugin mantis