skills.rest
schirrmacher
schirrmacherCOMMUNITY
Explore all skills by this author →
GitHub

deepreview

Audit public API interfaces across a codebase for consistency and simplification.

Updated Feb 23, 2026
Search Tags:#documentation#api#interfaces#audit#code-review#software-design#call-chains
One-click install
npx skills add https://github.com/schirrmacher/coding --skill deepreview-schirrmacher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deepreview
Source: https://github.com/schirrmacher/coding/tree/main/skills/deepreview
Command: npx skills add https://github.com/schirrmacher/coding --skill deepreview-schirrmacher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit interfaces in a codebase to verify consistency, surface area, and abstraction level across public APIs, then challenge mismatches and narrow surfaces.

Core Features & Use Cases

  • Inventory public interfaces across modules and folders to map the API surface.
  • Trace call-chains to understand who calls what and with which arguments.
  • Generate concrete findings and actionable recommendations to improve consistency and generalization.
  • Use cases include pre-release API reviews, onboarding new teams, and maintaining API hygiene over time.

Quick Start

Invoke the audit workflow on a target folder or file to reveal interface structures and recommended improvements.

Frequently Asked Questions about deepreview

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

FAQPage Schema
How do I audit API interfaces across my codebase for inconsistencies?▼

To audit API interfaces, you can analyze call-chains, parameter patterns, and surface area across public APIs to identify inconsistencies and propose concrete optimizations. This process helps verify consistency and narrow surface areas.

What is API surface area and when do I need to review it?▼

API surface area is the inventory of public interfaces across modules and folders that maps what external code can access. You need to review it during pre-release API reviews, team onboarding, or when maintaining API hygiene over time.

How do I trace call-chains to understand who calls what in my code?▼

Tracing call-chains involves analyzing who calls what and with which arguments across your codebase. This maps the flow of API usage and helps identify opportunities for simplification and improving generalization.

Can I audit private internal interfaces or does it only respect public API scope?▼

The audit requires and respects the public API scope by default, focusing on public interfaces across modules and folders. It targets inconsistencies in public surface area rather than private internal implementations.

What's the best way to simplify API interfaces before a release?▼

The best way to simplify API interfaces is to inventory public interfaces, trace call-chains, and analyze parameter patterns to surface concrete findings and actionable recommendations that improve consistency and generalization.

Does this code review process work for maintaining API hygiene over time?▼

Yes, this code review process works for maintaining API hygiene over time by continuously auditing interfaces to verify consistency, surface area, and abstraction level, then challenging mismatches and narrowing surfaces.

Related Skills

Explore More Software Engineering Skills→
joyehuangjoyehuang
3

deep-dive

Trace execution flows and analyze architectural patterns in source code.

Community
Advanced
yzavyasyzavyas
7

design

Analyze code, component, and API design quality for structural issues.

Community
Basic
RheasilviaRheasilvia

Debug Issue

Trace call chains and execution flows to identify root causes of software defects.

Community
Advanced
mrgeoffrichmrgeoffrich
3

update-api-artifacts

Rebuild API documentation and audit permissions from source code.

Community
Advanced