skills.rest
j4hr3n
j4hr3nCOMMUNITY
Explore all skills by this author →
GitHub

recon

Analyze git history and project metrics to generate a codebase health report.

Updated Mar 24, 2023
Search Tags:#codebase#reconnaissance#momentum#churn#bus-factor#bug-clustering
One-click install
npx skills add https://github.com/j4hr3n/dotfiles --skill recon-j4hr3n
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recon
Source: https://github.com/j4hr3n/dotfiles/tree/main/configs/claude-code/skills/recon
Command: npx skills add https://github.com/j4hr3n/dotfiles --skill recon-j4hr3n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codebase reconnaissance to provide a clear, honest health report before you start working on a project.

Core Features & Use Cases

  • Identify file churn hotspots, contributor bus-factor, bug clusters, project momentum, and firefighting patterns.
  • Great for onboarding to a new codebase, auditing a project, or planning refactors.
  • Use case: Provides a health briefing for a new repository to align on risks and priorities.

Quick Start

Tell me which repository to analyze or point me at a local path, and I'll generate a health report.

Frequently Asked Questions about recon

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

FAQPage Schema
How do I analyze codebase health and identify bug hotspots before a repo handover?▼

To analyze codebase health and identify bug hotspots before a repo handover, you can generate a reconnaissance report that leverages git history and commit messages to compute file churn, bus-factor risk, and bug clusters.

What is a bus-factor risk assessment and when do I need it for my project?▼

A bus-factor risk assessment evaluates contributor distribution within a codebase to identify dependencies on specific individuals. You need this project metric during onboarding, audits, or refactoring to align on operational risks.

How do I get a codebase health briefing for a local repository?▼

To get a codebase health briefing, point the analysis tool at your local repository path. It will process project metrics and deliver a structured, narrative report detailing firefighting patterns and file churn hotspots.

Does codebase reconnaissance work without external dependencies or components?▼

Yes, codebase reconnaissance works without external dependencies or components. It directly analyzes your repository's existing git history and commit messages to compute bug clusters and momentum.

What is the best way to measure file churn and project momentum during an audit?▼

The best way to measure file churn and project momentum during an audit is to compute git history metrics. This approach reveals health signals, bug hotspots, and firefighting patterns for a clear, actionable project view.

Related Skills

Explore More Software Engineering Skills→
26mitch2626mitch26

gstack-openclaw-retro

Analyze Git commit history to generate engineering retrospective reports.

Community
Advanced
thimsluggathimslugga

git-codebase-recon

Run git-based reconnaissance commands to surface codebase health signals.

Community
Advanced
dinoudondinoudon

code-quality-metrics

Assess code quality using cyclomatic complexity, test coverage, and maintainability metrics.

Community
Advanced
mahmoud20138mahmoud20138
10

real-time-risk-monitor

Monitor live portfolio exposure and drawdown with threshold-based alerts and kill switches.

Community
Advanced