git-health

Audit Git repositories and GitHub projects for configuration, secrets, and CI/CD issues.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Auto-one-Family/Automation-One --skill git-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-health
Source: https://github.com/Auto-one-Family/Automation-One/tree/main/.claude/skills/git-health
Command: npx skills add https://github.com/Auto-one-Family/Automation-One --skill git-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a thorough, read-only audit of a repository's Git and GitHub configuration to surface security risks, CI/CD issues, exposed secrets, branch protection gaps, and repo-hygiene problems so maintainers can prioritize fixes.

Core Features & Use Cases

  • Repository Inventory: Enumerates remotes, branches, tags, hooks, stashes, and unpushed commits with timestamps and context.
  • Secrets & .gitignore Analysis: Checks .gitignore coverage, searches for tracked sensitive files, and inventories potentially exposed credentials without revealing secrets.
  • CI/CD & Branch Strategy Review: Reads GitHub workflows, referenced secrets, CODEOWNERS and PR templates and provides actionable recommendations for branch protection and pipeline hygiene.
  • Use Case: Security or release engineers audit a codebase before open-sourcing or handing off to a new team to ensure no secrets, large assets, or stale branches remain.

Quick Start

Run the git-health skill to generate a read-only .claude/reports/current/GIT_HEALTH_REPORT.md summarizing remotes, unpushed commits, tracked sensitive files, CI workflows, and repo-hygiene findings.

Frequently Asked Questions about git-health

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

FAQPage Schema
How do I audit a GitHub repository for exposed secrets and configuration issues?

A repository health audit scans your Git state to detect exposed secrets, CI/CD misconfigurations, and branch protection gaps, producing a detailed Markdown report with command evidence and risky file listings.

Can I check for CI/CD misconfigurations and branch protection gaps without modifying files?

Yes, a read-only Git health audit analyzes GitHub workflows, CODEOWNERS, and PR templates to provide branch protection and CI/CD hygiene recommendations without modifying any repository files.

What does a repository health audit check for in tracked sensitive files?

A repository health audit checks tracked sensitive files by analyzing .gitignore coverage, inventorying potentially exposed credentials, and listing risky files while ensuring the actual secret values are never revealed.

Does the Git health audit work on unpushed commits and stale branches?

Yes, the Git health audit enumerates remotes, branches, tags, hooks, stashes, and unpushed commits with timestamps and context to identify stale branches and repository hygiene problems.

When should I run a repository health audit before open-sourcing a codebase?

You should run a repository health audit before open-sourcing a codebase or handing it off to a new team to ensure no secrets, large assets, or stale branches remain in the Git history.

What is the best way to review GitHub workflows and CODEOWNERS for pipeline hygiene?

The best way to review GitHub workflows and CODEOWNERS for pipeline hygiene is to run an audit that reads referenced secrets and PR templates, generating actionable recommendations for branch protection and CI configuration.