repo-health

Audit Git repositories for secrets, large files, and stale branches.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/eugener/cc-marketplace --skill repo-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-health
Source: https://github.com/eugener/cc-marketplace/tree/main/plugins/eugenes-tools/skills/repo-health
Command: npx skills add https://github.com/eugener/cc-marketplace --skill repo-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and helps you fix common issues in your Git repositories, ranging from security vulnerabilities like leaked secrets to performance bottlenecks caused by large files and general hygiene problems like stale branches.

Core Features & Use Cases

  • Comprehensive Audit: Scans for large blobs, tracked binary files, potential secrets, merge conflict markers, stale branches, missing .gitignore entries, commit hygiene, and uncommitted work.
  • Actionable Fixes: Provides exact commands to resolve identified issues.
  • Severity Grouping: Organizes findings into Critical, Warning, and Info categories.
  • Use Case: Before merging a large feature branch, run this audit to ensure no secrets were accidentally committed and that the repository is clean and optimized.

Quick Start

Run a full git repository health audit on the current repository.

Frequently Asked Questions about repo-health

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

FAQPage Schema
How do I scan a git repository for leaked secrets and security risks?

A git repository health audit scans commit history, file tracking, and repository structure to identify security risks and operational issues. This Skill categorizes findings into Critical, Warning, and Info groups, providing exact commands to resolve leaked secrets, stale branches, and large blobs.

How do I find and remove large binary files tracked in my git repository?

Finding large binary files requires analyzing repository structure and blob sizes to locate performance bottlenecks. This Skill detects tracked binary files and large blobs during its audit, providing actionable fix commands to remove them and optimize repository health.

What is the best way to clean up stale branches before merging a feature?

Cleaning up stale branches before merging requires auditing repository structure and branch states to identify abandoned work. This Skill detects stale branches and missing .gitignore entries as part of its comprehensive audit, providing categorized reports with exact commands for immediate resolution.

Does this git audit check for missing .gitignore entries and uncommitted work?

Yes, this git audit checks for missing .gitignore entries and uncommitted work alongside scanning for large blobs, potential secrets, and merge conflict markers. It analyzes commit history and file tracking to provide a categorized report with exact commands to resolve these hygiene issues.

Why should I run a repository hygiene audit before merging a large feature branch?

Running a repository hygiene audit before merging ensures no secrets were accidentally committed and verifies the repository is clean and optimized. This Skill identifies security vulnerabilities, large files, and stale branches, providing actionable fix commands categorized by severity for immediate resolution.