Codebase Analysis AI Agent Skill

Analyze repository evidence to bootstrap, migrate, update, or audit project documentation covering architecture, flows, APIs, schemas…

Context cost
24.2k tokensestimated from the bundle, loaded when it triggers
Bundle
44 files · 179.1 kB14 scripts among them — read before you run
Licence
Apache-2.0the author’s own terms
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

Analyze repository evidence to bootstrap, migrate, update, or audit project documentation covering architecture, flows, APIs, schemas, security, configuration, and delivery. Use when creating a complete documentation system, synchronizing existing docs with Git or code changes, adopting unmanaged documentation, checking documentation accuracy, or installing the supporting workflow. Prefer bounded Git-diff analysis for updates; use full-repository analysis only for explicit bootstrap requests. Do not use for generic writing, standalone code explanations, or code-quality reviews.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

documentation

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md16.5 kB · preview
--- name: codebase-analysis-ai ---
6# Codebase Analysis AI
7
8Keep repository documentation aligned with implementation changes while minimizing repository reads and repeated analysis.
9
10## Select an intent and execution plan
11
12Start with read-only discovery: resolve the repository and Git state. Run setup discovery with the current bundled skill command, python3 <installed-skill-root>/scripts/codebase_analysis_ai.py --root . setup-state --agents <active-host>, so an outdated project runtime cannot validate itself as current. Use python3 tools/codebase-analysis-ai/check.py check --mode working-tree for ordinary installed-runtime checks after setup is known to be current. On Windows, use py -3 in place of python3. Inspect documentation presence and collect only the bounded evidence needed to propose a plan. Do not begin substantive analysis, delegate, install automation, or write files before presenting one initial contract and receiving confirmation. If the setup state is ambiguous or conflicted, describe the conflict in that contract and never overwrite it silently.
13
14After discovery, resolve a primary intent and an ordered execution plan before reading additional references. A plan may combine modes when the context requires it, but must name every phase and briefly explain the expected final result. bootstrap may compose setup, structural migration, content update, generation, audit, and validation. migrate, update, and audit remain standalone modes when the repository is already configured. With no explicit mode or clear intent, include the proposed intent in the initial contract and ask the user to confirm it. Interpret requests such as “update the documentation” as update.
15
16- setup: Install the skill, persistent agent rules, deterministic runtime, Git hooks, or GitHub Action. Require either an explicit setup request or confirmation of a setup phase in the initial contract. After confirmation, installation of every missing component is mandatory; do not skip it or wait for a separate user request. Read references/setup-mode.md and references/automation.md.
17- bootstrap: Create or complete a documentation system and, when needed, scan the full repository. Require explicit bootstrap intent. Read references/bootstrap-mode.md, references/analyzer-profile-policy.md, references/project-taxonomy.md, references/document-style.md, and references/subagent-contract.md. After detecting the active host, read exactly one of references/host-codex.md, references/host-claude.md, references/host-gemini.md, or references/host-copilot.md.
18- update: Update existing documentation from current Git changes, a commit, or a commit range. This is the default synchronization mode. Reuse existing read-only analyzer profiles only for impacted macro-areas. Read references/update-mode.md, references/change-detection.md, references/impact-resolution.md, references/document-style.md, and references/subagent-contract.md when delegation is available.
19- audit: Inspect documentation accuracy, readability, language consistency, and link consistency without changing files. Reuse existing profiles for selected areas or all areas in a full audit. Read references/audit-mode.md, references/quality-rules.md, references/document-style.md, and references/subagent-contract.md when delegation is available.
20- migrate: Restructure existing documentation without performing a general evidence-based content refresh. It may move, rename, index, link, and normalize documents while preserving their useful content. Apply references/analyzer-profile-policy.md when delegation is needed; otherwise use the parent agent by default. Read references/migrate-mode.md, references/documentation-schema.md, references/naming-conventions.md, references/document-style.md, and references/subagent-contract.md when delegation is needed.
21
22Do not read references for unrelated modes.
23
24## Existing-documentation policy
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md2,139 words
Files44
LicenceApache-2.0
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈160
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
24,040
on trigger
The instruction body and 43 supporting files, read only when the skill fires.
12.1%
of a 200k window
Ten skills this size would not fit in the window together.
050k100k150k200k context window

24.2k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

44 files, 179.1 kB on disk. Mostly text — the instructions the model reads — with 14 scripts in it that your client would run only if the instructions tell it to. 4 files of its source are not in the download — listed after these, with why.

  • SKILL.md16.5 kB
  • agents/openai.yaml0.3 kB
  • references/analyzer-profile-policy.md5.6 kB
  • references/audit-mode.md3.1 kB
  • references/automation.md4.2 kB
  • references/bootstrap-mode.md4.7 kB
  • references/change-detection.md1.2 kB
  • references/document-style.md9.9 kB
  • references/documentation-schema.md2.9 kB
  • references/host-claude.md2.0 kB
  • references/host-codex.md2.0 kB
  • references/host-copilot.md2.5 kB
  • references/host-gemini.md2.4 kB
  • references/impact-resolution.md0.7 kB
  • references/migrate-mode.md2.8 kB
  • references/naming-conventions.md0.6 kB
  • references/project-taxonomy.md2.8 kB
  • references/quality-rules.md3.4 kB
  • references/setup-mode.md2.6 kB
  • references/subagent-contract.md9.0 kB
  • references/update-mode.md3.5 kB
  • scripts/codebase_analysis_ai.py9.5 kB
  • assets/adapters/AGENTS.md2.7 kB
  • assets/adapters/CLAUDE.md2.7 kB
  • assets/adapters/copilot-instructions.md2.7 kB
  • assets/adapters/GEMINI.md2.7 kB
  • assets/templates/area-readme.md0.6 kB
  • assets/templates/docs-index.md0.3 kB
  • assets/templates/project-readme.md0.7 kB
  • assets/templates/topic.md0.6 kB
  • assets/workflows/codebase-analysis-ai.yml1.1 kB
  • scripts/codebase_analysis_ai/__init__.py0.1 kB
  • scripts/codebase_analysis_ai/document_validator.py4.5 kB
  • scripts/codebase_analysis_ai/documentation_map.py16.6 kB
  • scripts/codebase_analysis_ai/documentation_preflight.py1.3 kB
  • scripts/codebase_analysis_ai/git_changes.py9.0 kB
  • scripts/codebase_analysis_ai/impact_graph.py1.5 kB
  • scripts/codebase_analysis_ai/link_validator.py6.8 kB
  • scripts/codebase_analysis_ai/path_filters.py1.1 kB
  • scripts/codebase_analysis_ai/project_detection.py5.0 kB
  • scripts/codebase_analysis_ai/project_installer.py17.1 kB
  • scripts/codebase_analysis_ai/setup_state.py7.7 kB
  • scripts/codebase_analysis_ai/source_hashes.py0.5 kB
  • scripts/codebase_analysis_ai/todo_scanner.py1.6 kB

Not in the download

Not carried is a type a skill download does not hold. Take them from its source.

  • assets/hooks/post-commitnot carried
  • assets/hooks/post-mergenot carried
  • assets/hooks/post-rewritenot carried
  • assets/hooks/pre-pushnot carried
What is not in it

A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 14 scripts beside the text, so the download is 44 files — not the whole of its source: 4 files are left out. They are listed under the files, with why. The Apache-2.0 licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Codebase Analysis AI · 24.2k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/codebase-analysis-ai/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/codebase-analysis-ai" ] && { [ ! -e .claude/skills/codebase-analysis-ai ] || { mv .claude/skills/codebase-analysis-ai "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/codebase-analysis-ai" .claude/skills/ && echo "Installed .claude/skills/codebase-analysis-ai"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add mattiaf95/codebase-analysis-ai

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/codebase-analysis-ai/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/codebase-analysis-ai/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/codebase-analysis-ai" ] && { [ ! -e ~/.claude/skills/codebase-analysis-ai ] || { mv ~/.claude/skills/codebase-analysis-ai "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/codebase-analysis-ai" ~/.claude/skills/ && echo "Installed ~/.claude/skills/codebase-analysis-ai" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/codebase-analysis-ai/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. Not in this download: 4 files of its source (the full list, and why). Take them from its source.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencemattiaf95/codebase-analysis-ai

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Who wrote it

MA
MattiaF95

Publishes on mcprush.

0 servers listed1 skill listednot claimed
Profile
Publisher
Servers0
Claim this skill