Skill

oco-inspect-repo-area

From oco

Structured codebase exploration with OCO-backed code intelligence. Auto-activates when the user asks to explore, understand, explain how a module works, a feature, an architecture, a data flow, or asks "how does this work", "where is", "show me", "what is this module". Enforces: compact summary before any action, selective reading (no directory dumps), explicit confidence level.

npx claudepluginhub hoklims/oco-marketplace

Tool Access

This skill uses the workspace's default tool permissions.

Preview

You are performing a focused exploration of a codebase area. Follow this structured workflow.

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

canvas-design

124.2k

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

20 files

anthropics-skills-13

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 31, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

OCO: Inspect Repository Area

You are performing a focused exploration of a codebase area. Follow this structured workflow.

Step 1: Identify the Target Area

Determine which part of the codebase needs exploration:

A module, package, or directory
A feature or capability
A data flow or interaction pattern

Step 2: Gather Ranked Context

Use oco.search_codebase if available (ranked, symbol-aware results):

oco.search_codebase({ query: "<area description>", workspace: "." })

Otherwise, use Grep for key symbols and Glob for file patterns.

Focus on symbol-level results — prefer targeted searches over raw file dumping.

Step 3: Read Key Files Selectively

Based on search results, read only the most relevant files. Do NOT dump entire directories.

Priority order:

Entry points and public API surfaces
Core types and data structures
Key implementation logic
Tests (for behavior documentation)

Step 4: Summarize Before Acting

Before taking any action, produce a compact summary:

Purpose of the area
Key types and their relationships
Entry points and data flow
Potential concerns or complexity hotspots

Rules

Never read more than 10 files without summarizing first
Prefer symbol-level inspection over full file reads
If an area is complex (>5 files), delegate to the @codebase-investigator subagent
Report confidence level: high / medium / low