Skill guide

Codebase exploration

Understand where behavior lives and how data, configuration, and ownership connect across a repository.

Answer a specific repository question by tracing entry points, calls, state changes, and relevant tests. The explanation connects verified facts to their source locations and makes unresolved links explicit.

Package version 0.1.0-beta.7

Included with Faye Coding Assistant

When to use

Use this when the deliverable is a repository map, behavior trace, explanation, or impact analysis before a change.

What to provide

  • The repository and the question you need answered.
  • A feature, symbol, route, configuration key, or directory that can bound the investigation.

Expected results

  • A concise map of responsibilities and execution or data flow.
  • Source evidence, relevant constraints, and clearly identified unknowns.

Example requests

Try this request

Codex
Codex request
$codebase-exploration Trace how a plugin manifest becomes a website detail page. Identify the input files, generated outputs, and the code that owns the page URL.
Grok
Grok request
/codebase-exploration Trace how a plugin manifest becomes a website detail page. Identify the input files, generated outputs, and the code that owns the page URL.
Antigravity
Antigravity request
/codebase-exploration Trace how a plugin manifest becomes a website detail page. Identify the input files, generated outputs, and the code that owns the page URL.

Requirements and limits

Before you start

  • Read access to the relevant repository and project instructions.

Scope and limitations

  • The workflow remains read-only and avoids commands that generate builds, dependencies, or caches.
  • It does not add an unsolicited implementation plan.
  • Repository reading that merely supports another task stays within that task.
Technical source

The hosted file belongs to the package version shown on this page.

plugins/faye-coding-assistant/skills/codebase-exploration

Open source file