Карта незнакомого репозитория
Быстро составляет карту незнакомого репозитория и выдаёт короткий документ-ориентир: точки входа, команды сборки, запуска и тестов, роли директорий, поток запросов и данных, ключевые абстракции и подводные камни, со ссылками на файлы. Используйте, когда пользователь впервые видит репозиторий или спрашивает, как устроен код.
codebase-explainerУстановка
Выполните одну команду — она сохранит SKILL.md в папку скиллов агента. Перезапустите агента, и он подхватит скилл сам.
mkdir -p ~/.claude/skills/codebase-explainer && curl -fsSL https://anymodel.org/en/skills/vibe-coding/codebase-explainer/SKILL.md -o ~/.claude/skills/codebase-explainer/SKILL.md
mkdir -p ~/.agents/skills/codebase-explainer && curl -fsSL https://anymodel.org/en/skills/vibe-coding/codebase-explainer/SKILL.md -o ~/.agents/skills/codebase-explainer/SKILL.md
New-Item -ItemType Directory -Force "$HOME\.claude\skills\codebase-explainer" | Out-Null; Invoke-WebRequest https://anymodel.org/en/skills/vibe-coding/codebase-explainer/SKILL.md -UseBasicParsing -OutFile "$HOME\.claude\skills\codebase-explainer\SKILL.md"
New-Item -ItemType Directory -Force "$HOME\.agents\skills\codebase-explainer" | Out-Null; Invoke-WebRequest https://anymodel.org/en/skills/vibe-coding/codebase-explainer/SKILL.md -UseBasicParsing -OutFile "$HOME\.agents\skills\codebase-explainer\SKILL.md"
Другой агент: сохраните файл в его папку скиллов или дайте ему ссылку на файл: https://anymodel.org/en/skills/vibe-coding/codebase-explainer/SKILL.md
SKILL.md
Codebase Explainer
Goal: in a few minutes of reading, give the user a map accurate enough to start changing the code. Read, do not modify. Every claim in the output must point to a file you actually opened.
Workflow
- Orient at the top level.
- List the root directory and read the README, then any
CONTRIBUTING,docs/, orAGENTS.md/CLAUDE.mdstyle notes. - Identify the language and framework from manifests:
package.json,pyproject.toml,go.mod,Cargo.toml,pom.xml,Gemfile,composer.json. - Check size:
git ls-files | wc -land a per-directory count help decide how deep to go.
- List the root directory and read the README, then any
- Find how to build, run and test. Look in manifest scripts,
Makefile,justfile,Dockerfile,docker-compose.yml, and CI files under.github/workflowsor similar. CI config is the most reliable source of the real commands. - Find the entry points: the
mainfile, the server bootstrap, the CLI command registry, the routes file, the job or worker starter. - Trace one representative path end to end. Pick a typical request, command or event and follow it from entry to storage and back, noting each file it passes through. One real trace is worth more than a directory-by-directory tour.
- Name the key abstractions: the 3 to 8 types, modules or tables that most other code depends on. Find them by searching for the most imported modules and the central data models or schemas.
- Collect the gotchas: required env vars (names only, never values), code generation steps, feature flags, migrations, monorepo boundaries, generated or vendored directories not to edit by hand, unusual conventions, and TODO or FIXME clusters.
- Optionally run the cheap, safe commands (install, test, lint) to confirm they work. Ask first before anything that touches external services or databases.
Useful commands
git log --oneline -n 15 # recent direction of work
git ls-files | head -100 # tracked layout
grep -rn "listen(" --include="*.js" --include="*.ts" --include="*.py" . # server start, adjust to the language
Output format
Write a short orientation doc, at most about 80 lines, in this shape:
# <Repo> orientation
What it is: one or two sentences.
Stack: language, framework, datastore.
Commands
- install: ... - run: ... - test: ... - lint/build: ...
(note which you verified and which you only read)
Layout
- `src/api/` : HTTP handlers (src/api/routes.ts defines all routes)
- ...
Flow: <request or event> -> `file:line` -> `file:line` -> storage
Key abstractions
- `User` model (src/models/user.ts): ...
Config: env var names and where they are read (src/config.ts)
Gotchas
- ...
Where to start: suggested first files to read for the user's likely task.
Use path:line references so the user can jump to code. Offer to save it as docs/ORIENTATION.md but do not create it unprompted.
Pitfalls
- Do not summarize from file names alone. Open the file before describing what it does.
- Do not paste large code blocks; reference them.
- Do not guess at commands. Mark anything unverified as "from README, not run".
- Do not list every directory. Cover those that matter for the user's goal and group the rest as "other".
- Never print the contents of
.envor credential files. List variable names only. - If the repo is huge or a monorepo, ask which package the user cares about and map that one deeply.
Source: AnyModel skills catalog · License: CC BY 4.0
Подключить через AnyModel API
Скилл работает на той модели, которую использует агент. Подключите Claude Code, Codex или Cursor к AnyModel и запускайте его на Claude, GPT, Gemini и других моделях по одному ключу — оплата за токены, без подписки.
AnyModel