Agent skill

Repo Audit

by zebbern in zebbern/claude-code-guide

Deep analysis of Git history: identify frequently changed hotspot files, analyze code ownership by contributor, and scan for leaked secrets.

MITAuto-check passedDevelopment

Install Repo Audit

skills CLI
$ npx skills add zebbern/claude-code-guide --skill repo-audit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install zebbern/claude-code-guide repo-audit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/zebbern/claude-code-guide.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/repo-audit .claude/skills/repo-audit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
repo-audit
GitHub stars
4.7k
Token cost
~831 tokens
SKILL.md length
322 words
Files
5 (incl. scripts)
Skills in repo
46
Repo updated
First seen
Licence
MIT

At a glance

Deep analysis of Git history: identify frequently changed hotspot files, analyze code ownership by contributor, and scan for leaked secrets.

  • Works in 3 steps: Hotspot File Analysis… → Code Ownership Analysis… → Secret Leak Scanning…
  • Tasks that involve Git workflow
  • SKILL.md covers Feature Overview, Use Cases and Dependencies
  • Runs Shell scripts from its folder; calls bash

What it does

Repo Audit is an agent skill from zebbern/claude-code-guide. Deep analysis of Git history: identify frequently changed hotspot files, analyze code ownership by contributor, and scan for leaked secrets. Triggered when users ask about Git analysis, code hotspots, who owns what code, secret scanning, security audits of commit history, or optimizing code review assignments.

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts (for example `scripts/hotfiles.sh`, `scripts/ownership.sh` and `scripts/secret-scan.sh`).

It sits in Development, covering Git workflow, Secrets management and Security review. It works with Git. The repository describes itself as: Claude Code Guide - Setup, Commands, workflows, agents, skills & tips-n-tricks from beginner to power user! The licence is MIT.

When your agent uses it

  • Tasks that involve Git workflow
  • Tasks that involve Secrets management
  • Tasks that involve Security review

Example prompts

  • “/repo-audit”

Requirements

  • A Bash shell

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Hotspot File Analysis (scripts/hotfiles.sh)
  2. Code Ownership Analysis (scripts/ownership.sh)
  3. Secret Leak Scanning (scripts/secret-scan.sh)

What it can do on your machine

Read from SKILL.md and the folder at commit 7ff9fbb. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Repo Audit loads about 831 tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 322 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~831

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from zebbern/claude-code-guide at commit 7ff9fbb, republished under its MIT licence (© zebbern). 322 words, ~831 tokens.

Download SKILL.mdSave it as .claude/skills/repo-audit/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
repo-audit
description
Deep analysis of Git history: identify frequently changed hotspot files, analyze code ownership by contributor, and scan for leaked secrets. Triggered when users ask about Git analysis, code hotspots, who owns what code, secret scanning, security audits of commit history, or optimizing code review assignments.
type
tool
license
MIT
tags
git, security, analysis, devops

Repo Audit — Deep Analysis of Git History

Perform three-dimensional analysis on a Git repository: hotspot file detection, code ownership analysis, and secret leak scanning.

Feature Overview

1. Hotspot File Analysis (scripts/hotfiles.sh)

Identify the most frequently changed files in a repository to help spot:

  • High-risk code areas (frequent changes = potential instability)
  • Files that deserve extra attention during code review
  • Modules that may need splitting or refactoring

Usage:

bash
bash scripts/hotfiles.sh [options]
OptionDescriptionDefault
--repo PATHRepository pathCurrent directory
--top NShow top N files20
--since DATEStart date (e.g. 2024-01-01)None
--until DATEEnd dateNone
--author AUTHORFilter by authorNone
--format FORMATOutput format: table / csv / jsontable
2. Code Ownership Analysis (scripts/ownership.sh)

Analyze actual code ownership, reporting for each contributor within the specified scope:

  • Commit count and percentage
  • Lines changed (additions/deletions)
  • Last active date

Usage:

bash
bash scripts/ownership.sh [options]
OptionDescriptionDefault
--repo PATHRepository pathCurrent directory
--path SUBPATHAnalyze a specific subdirectory or fileEntire repo
--top NShow top N contributors10
--since DATEStart dateNone
--format FORMATOutput format: table / csv / jsontable
3. Secret Leak Scanning (scripts/secret-scan.sh)

Scan the full Git history (including deleted commits) for common secrets and sensitive information:

  • AWS Access Key / Secret Key
  • GitHub / GitLab / Slack Tokens
  • SSH Private Keys
  • Generic API Keys, passwords, and secret patterns

Usage:

bash
bash scripts/secret-scan.sh [options]
OptionDescriptionDefault
--repo PATHRepository pathCurrent directory
--branch BRANCHScan a specific branchAll branches
--since DATEStart dateNone
--format FORMATOutput format: table / csv / jsontable
--severity LEVELMinimum severity level: low / medium / highlow

Use Cases

  • Security audits: Scan history for leaked secrets before deploying to production
  • Code review optimization: Identify hotspot files and prioritize reviewing high-risk areas
  • Team collaboration: Understand who knows which parts of the code best, and assign reviews accordingly
  • Tech debt assessment: Frequently changed files are strong candidates for refactoring

Dependencies

  • git (>= 2.20)
  • bash (>= 4.0)
  • Standard Unix utilities: awk, sort, head, grep

No additional dependencies or paid APIs required.

© zebbern, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts) in skills/repo-audit of zebbern/claude-code-guide.

  • SKILL.md
  • LICENSE
  • scripts/hotfiles.sh
  • scripts/ownership.sh
  • scripts/secret-scan.sh

Open the folder on GitHubat commit 7ff9fbb

Compare with similar skills

Repo Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Repo Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Repo Audit this skillzebbern/claude-code-guide4.7k—~831Automated safety check: PassMIT
Git Gh Pat AuthNEventStore/NEventStore1.6k—~828Automated safety check: PassMIT
Memstack Security Git Guardcwinvestments/memstack423—~3.1kAutomated safety check: NotesMIT
Openai Security Ownership Maptrailofbits/skills-curated5135 repos~2.2kAutomated safety check: NotesCC-BY-SA-4.0
Yao Workspace Git ConfigYaoApp/yao8.1k—~712Automated safety check: PassCustom licence
Repo SentinelMathews-Tom/armory329—~2.2kAutomated safety check: PassMIT

Similar skills

  • Git Gh Pat Auth

    NEventStore/NEventStore

    A skill your agent uses when: authenticating git and GitHub CLI for NEventStore tasks, fixing gh auth errors, setting PAT environment variables, preparing a shell session for git push and gh issue…

    1.6k GitHub stars~828 tokensUpdated 2 mo ago
    DevelopmentAuto-check passed
  • Memstack Security Git Guard

    cwinvestments/memstack

    A skill your agent uses when the user says 'git-guard', 'check git protection', 'is this repo protected', 'verify gitleaks', 'set up git hooks', 'install git-guard', or wants to confirm a repo…

    423 GitHub stars~3.1k tokensUpdated 14 days ago
    DevelopmentAuto-check: notes
  • Openai Security Ownership Map

    trailofbits/skills-curated

    Official

    Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization.

    513 GitHub starsUsed in 5 repos~2.2k tokens
    DevelopmentAuto-check: notes
  • Manages Git identity, HTTPS access tokens and SSH keys at the workspace level through three `tai tool` commands, each with a get, set, list, import or delete action.

    8.1k GitHub stars~712 tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Repo Sentinel

    Mathews-Tom/armory

    Full security audit for public repositories across 12 attack surfaces: git history, secrets, CI/CD, containers, dependencies, licenses.

    329 GitHub stars~2.2k tokensUpdated 5 days ago
    SecurityAuto-check passed
  • Release

    312362115/claude

    发版自动化技能:CalVer 版本号 + 从 git log 生成 changelog + GitHub Releases。

    107 GitHub stars~874 tokensUpdated 5 mo ago
    DevelopmentAuto-check passed

More from zebbern/claude-code-guide

All 46 skills in this repo
  • Localization Toolkit

    zebbern/claude-code-guide

    This skill should be used when setting up, auditing, or enforcing internationalization/localization in UI codebases (React/TS, i18next or similar, JSON locales), including installing/configuring the…

    4.7k GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed
  • Audit Flow

    zebbern/claude-code-guide

    Interactive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export.

    4.7k GitHub stars~4.2k tokensUpdated yesterday
    Auto-check passed
  • Chart Image

    zebbern/claude-code-guide

    Generate publication-quality PNG chart images from data, supporting line, bar, area, candlestick, pie, and heatmap charts.

    4.7k GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed
  • Code To Diagram

    zebbern/claude-code-guide

    Analyze codebases and automatically generate architecture diagrams, flowcharts, and org charts.

    4.7k GitHub stars~972 tokensUpdated yesterday
    Auto-check passed
  • Code Vuln Audit

    zebbern/claude-code-guide

    Scan code for security issues: dependency vulnerabilities (npm/pip audit), secret leaks (regex and entropy analysis), and OWASP anti-patterns like SQL injection, XSS, or command injection.

    4.7k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Idor Testing

    zebbern/claude-code-guide

    This skill should be used when the user asks to "test for insecure direct object references," "find IDOR vulnerabilities," "exploit broken access control," "enumerate user IDs or object references,"…

    4.7k GitHub starsUsed in 8 repos~3.1k tokens
    Auto-check passed

Works with

Questions about Repo Audit

What does Repo Audit do?

Deep analysis of Git history: identify frequently changed hotspot files, analyze code ownership by contributor, and scan for leaked secrets. Repo Audit is an agent skill from zebbern/claude-code-guide. Deep analysis of Git history: identify frequently changed hotspot files, analyze code ownership by contributor, and scan for leaked secrets.

When should I use Repo Audit?

Repo Audit fits situations like: tasks that involve Git workflow; tasks that involve Secrets management; tasks that involve Security review.

How do I install Repo Audit in Claude Code?

Run `npx skills add zebbern/claude-code-guide --skill repo-audit -a claude-code`. Or copy the skill folder (skills/repo-audit in zebbern/claude-code-guide) into .claude/skills/repo-audit in your project. Claude Code loads it when a task matches its description.

How do I install Repo Audit in Codex?

Run `npx skills add zebbern/claude-code-guide --skill repo-audit -a codex`. Or copy the skill folder (skills/repo-audit in zebbern/claude-code-guide) into .agents/skills/repo-audit in your project. Codex loads it when a task matches its description.

Can I use Repo Audit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add zebbern/claude-code-guide --skill repo-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/repo-audit, .gemini/skills/repo-audit, .github/skills/repo-audit and .opencode/skills/repo-audit in your project.

What does Repo Audit need to run?

Going by SKILL.md and its folder, Repo Audit needs a shell for the scripts in its folder and the command-line tools its instructions call (bash). Our summary lists: A Bash shell.

Does Repo Audit access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Repo Audit safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Repo Audit use?

Repo Audit is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Repo Audit use?

About 831 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Repo Audit?

Skills that share tags, products or a category with Repo Audit: Git Gh Pat Auth (NEventStore/NEventStore, 1.6k stars), Memstack Security Git Guard (cwinvestments/memstack, 423 stars), Openai Security Ownership Map (trailofbits/skills-curated, 513 stars) and Yao Workspace Git Config (YaoApp/yao, 8.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Repo Audit?

zebbern (a GitHub user) maintains it in zebbern/claude-code-guide, which has 4,650 GitHub stars. The repository holds 46 skills in this directory. The repository was last updated on October 10, 2026.

Source: zebbern/claude-code-guide on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.