repo-inspection

Name: repo-inspection
Availability: InStock
Author: Kartik

Analyze a repository to map structure, entry points, and source-of-truth files.

Updated Jul 17, 2026

Search Tags:#architecture #onboarding #codebase #audit #repository #inspection

Ready to run

npx skills add https://github.com/kartikkabadi/skills --skill repo-inspection

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repo-inspection
Source: https://github.com/kartikkabadi/skills/tree/main/repo-inspection
Command: npx skills add https://github.com/kartikkabadi/skills --skill repo-inspection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps an AI quickly build a reliable mental model of a repository so it can explain what exists, what is partially implemented, what is missing, and what is blocked.

Core Features & Use Cases

Repository survey: Identify the project structure, entry points, and important documentation.
Source-of-truth reading: Prioritize manifests, architecture files, core logic, config, and tests to understand the real state of the codebase.
Gap analysis: Distinguish working features from placeholders, shells, and unfinished work.
Use case: Ask it to inspect a repo before fixing bugs, planning changes, onboarding, or auditing implementation completeness.

Quick Start

Use the repo-inspection skill to analyze this repository and summarize what is built, partial, missing, and blocked.

Frequently Asked Questions about repo-inspection

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

FAQPage Schema

How do I analyze a codebase to understand its architecture and entry points?▼

To analyze a codebase, inspect repository manifests, core logic, configuration, and tests to map project structure and identify entry points for a reliable architecture review.

What is the best way to check implementation status and find missing features in a repository?▼

Checking implementation status requires reading source-of-truth files to perform gap analysis, distinguishing working repository features from placeholders, shells, and unfinished code.

How do I speed up codebase onboarding for a new developer?▼

Codebase onboarding accelerates by surveying repository documentation and core logic to build a mental model of what exists, what is partially implemented, and what is blocked.

Does an architecture audit detect placeholder code in a repository?▼

An architecture audit detects placeholder code by prioritizing source-of-truth reading of manifests and tests, separating real repository functionality from shells and unfinished work.

Can I use repository inspection to review implementation completeness before planning changes?▼

Repository inspection reviews implementation completeness by reading manifests, configuration, and tests, allowing you to map the codebase and verify what is built before planning changes.