inspect

Inspect codebases by discovering patterns and tracing call chains and dependencies.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/inkeep/team-skills --skill inspect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inspect
Source: https://github.com/inkeep/team-skills/tree/main/plugins/eng/skills/inspect
Command: npx skills add https://github.com/inkeep/team-skills --skill inspect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you build a structured understanding of a codebase area before making changes, by identifying patterns and tracing system flows.

Core Features & Use Cases

  • Pattern Inspection: Discover conventions, shared abstractions, and the "grain" of a code area.
  • System Tracing: Follow call chains, map dependencies, and identify the blast radius of changes.
  • Use Case: Before implementing a new feature in the authentication module, use this Skill to understand existing authentication patterns and trace how user sessions are currently managed across the system.

Quick Start

Inspect the 'auth' directory to understand its patterns and trace its dependencies.

Frequently Asked Questions about inspect

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

FAQPage Schema
How do I understand a codebase before implementing new features?

To understand a codebase, you inspect it for conventions, shared abstractions, and existing patterns. This builds a structured understanding of specific areas by tracing call chains and mapping dependencies before making changes.

What is the best way to trace call chains and map dependencies in a codebase?

Tracing call chains and mapping dependencies is done through system tracing to follow execution flows. This process identifies transitive dependencies and calculates the blast radius of changes for specific code areas.

How do I discover shared abstractions and conventions in unfamiliar code?

Discovering shared abstractions in unfamiliar code is achieved through pattern inspection. This analysis identifies the structural grain and shared conventions of a code area to ensure new implementations align with existing architecture.

Can I calculate the blast radius of changes before modifying dependencies?

Yes, you can calculate the blast radius of changes by analyzing transitive dependencies. Codebase inspection traces system flows and call chains to determine the exact impact of modifying specific dependencies or shared abstractions.

Does codebase inspection work for speccing and reviewing code flows?

Codebase inspection works for speccing, reviewing, and testing by analyzing conventions and tracing code flow. It builds structured understanding of system flows and transitive dependencies to support these specific engineering purposes.

Why do I need to inspect codebase patterns before modifying an authentication module?

You need to inspect codebase patterns to understand existing authentication flows and session management conventions. This prevents architectural mismatches by revealing shared abstractions, call chains, and the blast radius of your proposed changes.