codebase

Skills for understanding and improving an unfamiliar body of code.

Skills that operate on a codebase as a whole rather than on a change to it: getting oriented in an unfamiliar repository, finding where something is implemented, and surfacing what the code’s own shape suggests about what it needs next.

Nothing here assumes a project layout, a planning system, or a CLI beyond git.

Version	0.1.0
License	MIT
Skills	2

Install

/plugin install codebase@sdlc

Skills

Skill Description

api-enhancement-scan Given a library or module name, survey every call site of it across the codebase — fanning out subagents over independent codebase sections — and surface recurring caller-side patterns (repeated boilerplate, copy-pasted wrappers, awkward argument plumbing, repeated post-processing) that a new or enhanced API on the called module would absorb. Returns ranked enhancement opportunities, each backed by real call-site citations. Use when asked to find API improvement or enhancement opportunities for a module, library, or package, to spot missing affordances, or to understand how a module is actually used by its callers. Pass --in to survey only named packages or directories instead of the whole project, and --workflow to have it propose a reusable Workflow script for the survey instead of running it ad hoc.

explore-codebase Systematic method for understanding an unfamiliar codebase: getting oriented in a new repo, locating where something is implemented, tracing how a feature or request flows end to end, and building an accurate mental model before answering questions or making changes. Use whenever you're dropped into a repo or the user asks things like "how does X work here", "where is Y handled", "how is this project structured", "help me understand this codebase", "onboard me to this code", "find where Z is implemented", or "explore this repo and write up notes" — or before editing code you haven't read yet. Can optionally save the resulting map as a markdown file, a linked Obsidian-style vault, or a self-contained HTML page carrying diagrams of the structure it found.

Skill	Description
`api-enhancement-scan`	Given a library or module name, survey every call site of it across the codebase — fanning out subagents over independent codebase sections — and surface recurring caller-side patterns (repeated boilerplate, copy-pasted wrappers, awkward argument plumbing, repeated post-processing) that a new or enhanced API on the called module would absorb. Returns ranked enhancement opportunities, each backed by real call-site citations. Use when asked to find API improvement or enhancement opportunities for a module, library, or package, to spot missing affordances, or to understand how a module is actually used by its callers. Pass --in to survey only named packages or directories instead of the whole project, and --workflow to have it propose a reusable Workflow script for the survey instead of running it ad hoc.
`explore-codebase`	Systematic method for understanding an unfamiliar codebase: getting oriented in a new repo, locating where something is implemented, tracing how a feature or request flows end to end, and building an accurate mental model before answering questions or making changes. Use whenever you're dropped into a repo or the user asks things like "how does X work here", "where is Y handled", "how is this project structured", "help me understand this codebase", "onboard me to this code", "find where Z is implemented", or "explore this repo and write up notes" — or before editing code you haven't read yet. Can optionally save the resulting map as a markdown file, a linked Obsidian-style vault, or a self-contained HTML page carrying diagrams of the structure it found.