codebase-recon — Claude Code plugin: Git history analysis
The codebase-recon plugin reads a repository’s Git history to map the project before you inspect its code. Use it to spot risky files, knowledge concentration, and shifts in team activity.
MIT ★ 1,596 updated 2026-10-29
/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install codebase-recon@awesome-codex-pluginsWhat codebase-recon does
The plugin first gauges repository size, then examines seven areas in parallel: frequently changed files, bug fixes, knowledge concentration, team momentum, emergency fixes and reverts, recently added files, and active contributors. It cross-checks change hotspots against files that attract bug fixes to flag areas of higher risk.
The report includes recommendations based on its findings. It needs git and a repository with commit history; without that history, there is nothing to analyze. Run /codebase-recon when you’re orienting yourself in an unfamiliar codebase.
What it helps with
- find files that change frequently
- spot files that attract repeated bug fixes
- see whether project knowledge is concentrated among contributors
- check development momentum and emergency-fix activity
- identify higher-risk files from Git history
Example prompts for the agent
- Analyze this repository’s Git history and flag higher-risk files:
/codebase-recon. - Before I inspect the code, show how the project has changed and who is active:
/codebase-recon. - Check where project knowledge is concentrated and how often emergency fixes happen:
/codebase-recon.
How to install codebase-recon
Plugin marketplace
/plugin marketplace add hashgraph-online/awesome-codex-plugins/plugin install codebase-recon@awesome-codex-pluginsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about codebase-recon
How do I install codebase-recon in Claude Code?
Run /plugin marketplace add hashgraph-online/awesome-codex-plugins, then /plugin install codebase-recon@awesome-codex-plugins. Open the plugin browser with /plugin.
What does codebase-recon do?
It examines Git history across seven areas, compares change hotspots with files that draw bug fixes, and reports findings with recommendations.
What does codebase-recon need to run?
It requires git and a repository with commit history.
Source text
codebase-recon-skill · MIT
# codebase-recon-skill A coding agent skill that analyzes git history to understand a codebase before reading any code. Reveals project health, risk areas, team structure, and development momentum. Inspired by ["The Git Commands I Run Before Reading Any Code"](https://piechowski.io/post/git-commands-before-reading-code/) by [Ally Piechowski](https://github.com/grepsedawk). ## Installation ### Via skills.sh (works with 20+ coding agents) ```sh npx skills add yujiachen-y/codebase-recon-skill ``` Works with Claude Code, Cline, Cursor, GitHub Copilot, Gemini CLI, and any agent supporting the [Agent Skills Specification](https://agentskills.io/specification). ### Via Claude Code plugin system ``` /plugin marketplace add yujiachen-y/codebase-recon-skill ``` Then install the plugin from the marketplace browser via `/plugin`. ### Via Codex plugin system ```sh codex plugin marketplace add yujiachen-y/codebase-recon-skill ``` Then run `/plugins` in Codex, choose the `Codebase Recon` marketplace, and install `codebase-recon`. ## Usage In your coding agent, invoke: ``` /codebase-recon ``` The skill will: 1. **Probe** the repo to determine its scale (small / medium / large) 2. **Analyze** 7 dimensions in parallel: code hotspots, bus factor, bug magnets, team momentum, firefighting frequency, recently added files, and active contributors 3. **Cross-reference** hotspots with bug magnets to identify high-risk files 4. **Report** findings with actionable recommendations ## What You'll Learn | Dimension | Question Answered | |-----------|-------------------| | Code Hotspots | Which files change the most? | | Bug Magnets | Which files attract the most bug fixes? | | High-Risk Files | Which files are both hot AND buggy? | | Bus Factor | Who knows what? Is knowledge concentrated? | | Team Momentum | Is development accelerating, stable, or declining? | | Firefighting | How often are there emergency fixes and reverts? | | Recently Added | Where is active development happening? | ## Requirements - `git` (any version) - A git repository with commit history ## Attribution This skill is inspired by ["The Git Commands I Run Before Reading Any Code"](https://piechowski.io/post/git-commands-before-reading-code/) by [Ally Piechowski](https://github.com/grepsedawk). The original article describes 5 git commands for codebase reconnaissance. This skill extends the concept with auto-scaling, cross-referencing, and actionable recommendations. ## License [MIT](LICENSE)
© Jiachen Yu · MIT · hashgraph-online/awesome-codex-plugins