repo-audit
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.
- License 许可
- MIT
- 最近更新
- 2026-10-27
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- repo-audit
- tags
- [ "git", "security", "analysis", "devops" ]
- type
- tool
- license
- MIT
- 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.
02 资源文件 4
- 许可证LICENSE1.1 KB
- 脚本scripts/hotfiles.sh3.6 KB
- 脚本scripts/ownership.sh5.0 KB
- 脚本scripts/secret-scan.sh9.2 KB
03 SKILL.md 正文
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 scripts/hotfiles.sh [options]
| Option | Description | Default |
|---|---|---|
--repo PATH |
Repository path | Current directory |
--top N |
Show top N files | 20 |
--since DATE |
Start date (e.g. 2024-01-01) |
None |
--until DATE |
End date | None |
--author AUTHOR |
Filter by author | None |
--format FORMAT |
Output format: table / csv / json |
table |
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 scripts/ownership.sh [options]
| Option | Description | Default |
|---|---|---|
--repo PATH |
Repository path | Current directory |
--path SUBPATH |
Analyze a specific subdirectory or file | Entire repo |
--top N |
Show top N contributors | 10 |
--since DATE |
Start date | None |
--format FORMAT |
Output format: table / csv / json |
table |
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 scripts/secret-scan.sh [options]
| Option | Description | Default |
|---|---|---|
--repo PATH |
Repository path | Current directory |
--branch BRANCH |
Scan a specific branch | All branches |
--since DATE |
Start date | None |
--format FORMAT |
Output format: table / csv / json |
table |
--severity LEVEL |
Minimum severity level: low / medium / high |
low |
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.
04 同仓库更多 Skills
typescript-pro
Use when building TypeScript applications requiring advanced type systems, generics, or full-stack type safety. Invoke for type guards, utility types, tRPC integration, monorepo setup.
tos-clause-scanner
Audit Terms of Service, user agreements, and privacy policies for consumer risks, producing a structured report that flags unfair clauses, data traps, and liability issues. Trigger when a user asks to review, audit, or analyze a ToS, privacy policy, or user agreement, or mentions specific concerns like auto-renewal or data authorization.
timeline-builder
Generate beautiful interactive timeline HTML pages from JSON data, with vertical, horizontal, or dual-side layouts, collapsible details, and custom colors. Ideal for project milestones, company histories, or resumes. Triggered when a user mentions 'timeline', 'history of events', 'project milestones', 'release log', or asks to visualize a chronological sequence of data.
three-best-practices
Three.js performance optimization and best practices guidelines. Use when writing, reviewing, or optimizing Three.js code. Triggers on tasks involving 3D scenes, WebGL/WebGPU rendering, geometries, materials, textures, lighting, shaders, or TSL.
test-suite-architect
This skill should be used when establishing comprehensive QA testing processes for any software project. Use when creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics, or generating progress reports. Includes autonomous execution capability via master prompts and complete documentation templates for third-party QA team handoffs. Implements OWASP security testing and achieves 90% coverage targets.
test-driven-dev
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.