recon-project

Generates a deterministic RECON.md inventory report of a project directory before manual file reading.

1|1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/gabesan21/project-of-projects --skill recon-project-gabesan21
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recon-project
Source: https://github.com/gabesan21/project-of-projects/tree/main/.agents/skills/recon-project
Command: npx skills add https://github.com/gabesan21/project-of-projects --skill recon-project-gabesan21

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Understanding an unfamiliar project directory normally requires opening files one by one, which wastes time and context. This Skill produces a deterministic inventory report covering the tree, languages, manifests, git hotspots, and entry points so you know what is worth reading before you start. ## Core Features & Use Cases - Deterministic project inventory: Runs scripts/pop_recon.py (stdlib only, zero LLM) to produce a RECON.md with tree, languages/LOC, manifests, git churn hotspots, and entry points/configs/CI. - Writing mode for markdown bases: For mostly-markdown directories, the report switches to chapter/heading structure, wordcounts, and a frontmatter inventory instead of code metrics. - Use Case: At the start of a delegated recon or during task planning that requires broad reading, generate the RECON.md of the target directory, pass it to subagents as context, and only then open the specific files the report could not answer. ## Quick Start Run the pop_recon.py script on the target project directory and read the generated RECON.md report in full before opening any project file.

Frequently Asked Questions about recon-project

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

FAQPage Schema
How do I quickly understand an unfamiliar codebase before reading files?▼

Generate a deterministic inventory report with pop_recon.py, which outputs the directory tree, languages and LOC, manifests, git churn hotspots, and entry points. Read that report first, then open only the specific files it could not answer.

How to generate a project structure report with Python?▼

Run `python3 scripts/pop_recon.py <dir>` to print the report to stdout, or add `--output RECON.md` to write it to a file. The script uses only the Python standard library and requires no external dependencies.

Does the recon report work without a git repository?▼

Yes. When the target directory has no .git folder, the hotspots section degrades with an explicit note, while the tree, languages, manifests, and entry point sections remain fully intact.

Can I use project recon on markdown or documentation folders?▼

Yes. For mostly-markdown bases the report switches to writing mode, showing chapter and heading structure, wordcounts, and a frontmatter inventory instead of code languages and LOC metrics.

Should the RECON.md report be committed to the repository?▼

No. RECON.md is a derived artifact regenerated on demand and is never committed as a source of truth. Durable knowledge belongs in specs, DOX contracts, and memory files, not in the recon report.