engdirs-status

Audit .eng/ git repositories for dirty files, unpushed commits, and branch information.

2|Updated Jun 15, 2026
One-click install
npx skills add https://github.com/jmerkow/my-agentic-stuff --skill engdirs-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engdirs-status
Source: https://github.com/jmerkow/my-agentic-stuff/tree/main/plugins/eng-ops/skills/engdirs-status
Command: npx skills add https://github.com/jmerkow/my-agentic-stuff --skill engdirs-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill allows users to audit their .eng/ git repositories to check their status, unpushed commits, and ensure they are up-to-date and properly initialized.

Core Features & Use Cases

  • Repo Status: Report which .eng/ repositories are dirty, have unpushed commits, or are uninitialized.
  • Branch Information: Provide details on the current branch and any ahead/behind changes.
  • Dirty Files: Show which files in a repository are uncommitted and require attention.
  • Use Case: When a user is unsure about the state of their .eng/ repositories and needs to ensure they are ready for further development or release.

Quick Start

Check the status of your .eng/ repositories by running the command 'audit.sh'.

Frequently Asked Questions about engdirs-status

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

FAQPage Schema
How do I check git repository status for unpushed commits?

To check git repository status for unpushed commits, run the audit script to identify dirty files, unpushed commits, and ahead/behind branch changes across your repositories.

What is a git repo audit and when do I need it?

A git repo audit reports repository health by checking for uninitialized, dirty, or unpushed states. You need it during daily maintenance to ensure your repositories are ready for development or release.

Can I monitor multiple git repositories for dirty files at once?

Yes, you can monitor multiple git repositories for dirty files by running the audit script, which reports uncommitted files and branch information across all targeted repositories.

Do I need git command experience for repository status auditing?

Yes, you need basic familiarity with git commands to effectively use the repository status auditing script and interpret the reported branch and unpushed commit information.

What's the best way to maintain daily repository health?

The best way to maintain daily repository health is running an audit script that checks for uninitialized, dirty, or unpushed states to ensure your codebase is properly updated.

Why does my git repository audit show uninitialized status?

Your git repository audit shows uninitialized status when repositories lack proper git initialization, preventing the script from tracking dirty files, unpushed commits, and branch information.