git-recon

Analyze GitHub commit histories and diffs to detect unpatched security gaps.

1|Updated Mar 20, 2026

Search Tags:#git #code review #security #vulnerability #diff #commit analysis #call graph

Ready to run

npx skills add https://github.com/enderphan94/pentest-kit --skill git-recon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-recon
Source: https://github.com/enderphan94/pentest-kit/tree/main/skills/git-recon
Command: npx skills add https://github.com/enderphan94/pentest-kit --skill git-recon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps security researchers and developers discover vulnerabilities that are present in the commit history of target repositories, especially unpatched security gaps.

Core Features & Use Cases

Commit-History Analysis: Clones repositories and searches through recent commits for security-related keywords.
Patch Diff Inspection: Analyzes changes in suspect commits to identify functions and code areas potentially left unpatched.
Sibling-Caller Detection: Finds instances in the codebase where similar functions lack the necessary guards, revealing patch gaps.
Use Case: A security analyst wants to find outdated or overlooked security checks in open-source projects to prioritize vulnerability assessments.

Quick Start

Use the git-recon skill to analyze a specific public GitHub repository URL for potential security gaps.

Frequently Asked Questions about git-recon

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

FAQPage Schema

How do I find unpatched security issues in public GitHub repositories?▼

You can find unpatched security issues by analyzing commit histories and patch diffs. This Skill inspects recent commits for security keywords and examines code call graphs to identify functions lacking necessary guards.

How does analyzing commit history help discover vulnerabilities?▼

Analyzing commit history reveals vulnerabilities by searching recent commits for security-related changes. It inspects diffs to identify suspect code areas and detects sibling-callers where similar functions lack the necessary security guards.

Can I use this to detect patch gaps in open-source projects?▼

Yes, you can detect patch gaps in open-source projects by analyzing code call graphs. The process finds instances in the codebase where similar functions lack necessary guards, revealing overlooked security checks for targeted assessments.

Do I need GitHub API access for repository commit analysis?▼

Yes, you need GitHub API access and clone permissions to perform repository commit analysis. These permissions allow the tool to clone repositories and search through commit histories and diffs for security gaps.

What is the best way to inspect diffs for security-related code changes?▼

The best way to inspect diffs for security changes is to analyze suspect commits to identify functions and code areas left unpatched. This pinpoints exact locations where security guards are missing in the updated codebase.