Skip to content
Agentmart
Submit a tool

codebase-analysis

Inspect and map an existing repository before making significant changes.

Skill by PHENOMVALENCE

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/phenomvalence-codebase-analysis

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Inspect and map an existing repository before making significant changes. Use when onboarding to a project, planning a feature, debugging unfamiliar code, or determining architecture.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/codebase-analysis

What's inside

Skill name
codebase-analysis
Description
Inspect and map an existing repository before making significant changes. Use when onboarding to a project, planning a feature, debugging unfamiliar code, or determining architecture.
License
MIT
Instructions
23 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Codebase Analysis

## Goal
Build an evidence-based mental model of the repository before editing.

## Workflow
1. Read `AGENTS.md`, `README.md`, project docs, and package manifests.
2. Identify framework versions, runtime, package manager, database, auth, queues, storage, external APIs, CI, and deployment model.
3. Map the relevant request path from entry point to persistence/external side effects.
4. Find similar existing implementations and reuse project conventions.
5. Inspect relevant tests and fixtures.
6. Identify risk areas: migrations, auth, permissions, external integrations, shared components, public contracts.
7. Summarize findings before proposing changes.

## Output
Provide a concise architecture map, relevant files, dependencies, data flow, constraints, and unknowns.

## Rules
- Do not infer what can be verified from code.
- Do not start large edits while core behavior is still unclear.
- Prefer repository conventions over generic patterns unless the existing design is demonstrably unsafe or unsuitable.

From PHENOMVALENCE/engineering-agent-skills, MIT.

More from PHENOMVALENCE/engineering-agent-skills

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Sep 16, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from PHENOMVALENCE

Cite this page

codebase-analysis skill. Agent Mart. https://agentmart.dev/skills/phenomvalence-codebase-analysis (last updated 2026-10-24)