One-click install
npx skills add https://github.com/iadr-dev/colab --skill explore-codebase-iadr-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explore-codebase
Source: https://github.com/iadr-dev/colab/tree/main/skills/explore-codebase
Command: npx skills add https://github.com/iadr-dev/colab --skill explore-codebase-iadr-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Explore-codebase turns an unfamiliar repository into a clear, navigable understanding so you can move from guesswork to confident implementation.

Core Features & Use Cases

  • Systematic codebase discovery: Reads project meta, identifies entry points, checks tests, and performs source spot checks.
  • Actionable project mapping: Writes a populated .ohc/PROJECT.md with stack, architecture, conventions, entry points, and gotchas.
  • Tooling assist for accurate detection: Uses provided generator scripts to auto-detect the tech stack and fill the tech stack table.

Use cases: Start-of-project onboarding, entering a new feature area, and resuming after a long gap where prior context has been forgotten.

Quick Start

Run node skills/explore-codebase/scripts/generate-project-map.js to auto-detect the repository’s tech stack and set up the .ohc/PROJECT.md groundwork.

Frequently Asked Questions about explore-codebase

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

FAQPage Schema
How do I onboard onto an unfamiliar codebase for implementation readiness?

Map an unfamiliar codebase by reading project metadata, checking CI, and identifying entry points. This systematic codebase exploration generates a structured overview of architecture and conventions, moving you from guesswork to confident implementation.

What is the best way to document project architecture and conventions for developer onboarding?

Document project architecture by running a script to auto-detect the tech stack and populate a project map. This generates a structured markdown file capturing stack details, entry points, and gotchas for seamless developer onboarding.

How can I quickly map a new feature area when I have forgotten prior project context?

Map a new feature area by performing source spot checks and reading representative files to rebuild project context. This approach extracts architecture and conventions, writing findings into a dedicated project map file for quick recovery.

Does this codebase exploration approach work without external dependencies?

Yes, codebase exploration works without external dependencies. It operates by reading key metadata, tests, and representative source files directly from the repository, using provided generator scripts to auto-detect the tech stack.

How do I auto-detect a repository's tech stack for engineering documentation?

Auto-detect a repository's tech stack by executing the provided generator script. This script analyzes the codebase and automatically populates a tech stack table within your engineering documentation file.