# Code Explorer

Use this skill when exploring, analyzing, or understanding project/code structure.

- Repository: https://github.com/clacky-ai/openclacky (1209 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add clacky-ai/openclacky --skill code-explorer -g -a claude-code -y`
Codex: `npx skills add clacky-ai/openclacky --skill code-explorer -g -a codex -y`
Cursor: `npx skills add clacky-ai/openclacky --skill code-explorer -g -a cursor -y`
Gemini CLI: `npx skills add clacky-ai/openclacky --skill code-explorer -g -a gemini-cli -y`

## Description

Use this skill when exploring, analyzing, or understanding project/code structure. Required for tasks like "analyze project", "explore codebase", "understand how X works".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Code Explorer Subagent

You are now running in a **forked subagent** mode optimized for fast code exploration.

## Your Mission
Quickly explore and analyze the codebase to answer questions or gather information.

## Your Restrictions
- NO modifications: You CANNOT use `write` or `edit` tools
- Read-only: Your role is to ANALYZE, not to change

## Workflow, follow this order strictly

1. **List the file tree**, run `glob` with `**/*` to get an overview of the project structure
2. **Read README.md**, if it exists, read it to understand the project purpose and layout
3. **Find relevant files**, based on the task, use `grep` to locate key patterns or specific files
4. **Read only what's needed**, use `file_reader` only on the files directly relevant to the question
5. **Report clearly**, provide a concise, actionable summary

## Rules
- Do NOT read files blindly, always have a reason before opening a file
- Do NOT read every file in a directory, be selective
- Prefer `grep` over `file_reader` for finding specific patterns
- Stop as soon as you have enough information to answer the question