skills.rest
brmatola
brmatolaCOMMUNITY
Explore all skills by this author →
GitHub

investigating-a-codebase

Verify codebase state by locating files and tracing component relationships.

Updated Jan 17, 2026
Search Tags:#architecture#documentation#codebase#verification#patterns#tracing#investigate
One-click install
npx skills add https://github.com/brmatola/gremlins --skill investigating-a-codebase-brmatola
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigating-a-codebase
Source: https://github.com/brmatola/gremlins/tree/main/skills/investigating-a-codebase
Command: npx skills add https://github.com/brmatola/gremlins --skill investigating-a-codebase-brmatola

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Understand and validate the current codebase state to ground planning decisions in reality, preventing hallucinations about what exists or how it is structured. This Skill helps teams confirm file existence, architecture patterns, and component relationships before committing to design choices.

Core Features & Use Cases

  • Verify existence and location of entry points, modules, and configuration.
  • Trace imports, references, and component relationships to map architecture.
  • Provide definitive answers about patterns and structures to support design decisions.
  • Use cases include verifying that authentication flows exist, locating API surface, and confirming directory layouts.

Quick Start

To start, describe a design assumption or feature you'd like to validate and ask the Skill to locate and report concrete evidence from the codebase.

Frequently Asked Questions about investigating-a-codebase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify existing architecture patterns in a codebase before planning new features?▼

To verify architecture patterns in a codebase, you can apply systematic search strategies and cross-reference traces to locate existing modules, trace imports, and provide definitive evidence of component relationships before making design decisions.

What is the best way to trace imports and component relationships across a project?▼

Tracing imports and component relationships requires cross-reference traces and systematic search strategies to map architecture, proving the exact existence and location of files and configuration entry points across the project.

How do I confirm file existence and directory layouts to prevent hallucinations during design?▼

Confirming file existence and directory layouts requires explicit evidence reporting, using systematic search strategies to prove the exact location of components and configuration files, grounding your design decisions in verified reality.

Can I use this approach to locate API surface and verify authentication flows?▼

Yes, you can locate API surface and verify authentication flows by applying systematic search strategies to trace references and map component relationships, producing definitive findings about what currently exists.

When do I need to investigate a codebase for design decisions?▼

You need to investigate a codebase when confirming architecture choices, locating existing patterns, or validating the current state of files and components before committing to new design decisions and planning features.

Related Skills

Explore More Software Engineering Skills→
buiminhduc23011buiminhduc23011

awf-debug

Translate stack traces into human-readable explanations and suggest verified code fixes.

Community
Advanced
wyattjohwyattjoh
1

research-augmented-design

Verify technical hypotheses and API constraints with parallel background research agents.

Community
Advanced
rjroyrjroy
6

ddp

Generate Mermaid diagrams for data flows, class relationships, and architectures.

Community
Basic
EotelEotel

update-codemaps

Analyze TypeScript/Node.js codebases to update codemaps with architecture maps and diffs.

Community
Advanced