# Proactive Directory Exploration

> proactive-directory-exploration

- Skill: `claudiawong522/proactive-directory-exploration` (Agent Skill)
- Install (CLI): `npx skillmds@latest add claudiawong522/proactive-directory-exploration`
- Raw SKILL.md: https://api.skillmd.com/api/skills/claudiawong522/proactive-directory-exploration/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: claudiawong522 (https://skillmd.com/u/claudiawong522)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/claudiawong522/proactive-directory-exploration

---

# proactive-directory-exploration

Automatically explore directory contents and examine key files after navigation to understand context without waiting for further instructions.

# Proactive Directory Exploration

When you navigate to a new directory, take initiative to understand its structure and contents before proceeding with your task.

## Steps

1. **List directory contents** - Run `ls -la` (or `dir` on Windows) to see all files and folders
2. **Identify key files** - Look for common indicators like:
   - `README.md` or `README.txt` - project documentation
   - `package.json`, `requirements.txt`, `Gemfile` - dependency/project config
   - `Makefile`, `build.sh`, `.github/workflows/` - build/automation scripts
   - `.gitignore`, `LICENSE` - project metadata
3. **Examine critical files** - Cat or preview the most relevant files (README first, then config files)
4. **Summarize findings** - Share what you discovered about the project structure and purpose
5. **Await next instruction** - Now you're ready to proceed with informed context

## Why This Works

- **Saves time** - You understand the project before making assumptions
- **Prevents mistakes** - You avoid commands that might break things
- **Improves quality** - Context leads to better, more relevant solutions
- **Shows initiative** - Users appreciate proactive problem-solving

## Tips

- Check for hidden files (starting with `.`) as they often contain important configuration
- Skim README files quickly for setup instructions or key concepts
- Look for test files or examples to understand how the code is meant to be used
- If the directory is large, focus on the root level first before diving deeper