repo-hygiene

To audit a git repository for stale files and gaps, run an automated hygiene check that analyzes git logs, git status, and file system sizes to detect untouched scripts, missing .gitignore patterns, and unpushed commits, generating a structured report for review.

Repository hygiene maintenance includes detecting stale Python scripts untouched for over 60 days, verifying .gitignore patterns, checking archive compliance, flagging large files, and reporting on diverged or orphaned branches to ensure the repository is clean before a release.

Yes, you can check for unpushed commits and orphaned branches during a repository audit. The sync health feature analyzes git status to report on diverged branches, orphaned branches, and unpushed commits, flagging potential synchronization issues for review.

To identify large files and documentation freshness issues, the audit checks overall repository size against thresholds and flags Markdown documentation files not updated within specified timeframes, analyzing file system sizes and modification dates to surface warnings.

Yes, the repository audit works without external dependencies. It requires no additional packages, relying on scripts and references to analyze git logs, git status, and file system metadata directly to generate its structured hygiene report.

Automated .gitignore auditing verifies essential patterns are present and flags untracked files that should be ignored, but it relies on predefined essential patterns and cannot infer project-specific ignore rules or dynamically adjust to novel framework outputs.