git-dirty-check

A narrow git skill for summarizing uncommitted changes in a local repository. It groups staged, unstaged, untracked, and conflicted entries, applies conservative path- and filename-based risk flags, and suggests up to three next checks without modifying repo state.

git-dirty-check is a deliberately narrow skill for one job: understanding the current uncommitted state of a local git repository.

It does not try to manage branches, write commit messages, resolve conflicts, review pull requests, or act as a general git assistant. Instead, it gives a compact, structured triage of the current working tree:

• repo state
• changed entries by category
• conservative risk flags based mostly on paths, filenames, and diff stats
• a few copy-paste-ready next checks
• explicit omissions when details are capped or sensitive

The skill is read-only. It is designed for developers who want a quick operational summary before a commit, handoff, or local review, without granting write access or triggering broader repo assistance.

It also applies strict limits to deeper inspection:

• fail fast if the target is not a git repo
• branch metadata is optional
• deep diff inspection is capped
• secret-bearing filename patterns are handled at filename level only

This skill is most useful when raw git output is technically sufficient, but slower to parse than a stable triage summary.

Workflow

1. Confirm the target path is inside a git repository.
2. If it is not a git repository, stop immediately and say so.
3. Collect read-only repo state with git status and diff-stat commands.
4. Group changed entries into:
   • staged
   • unstaged
   • untracked
   • conflicted
5. Apply conservative risk flags based mostly on file paths and filenames.
6. Inspect diff content only when filename and diff-stat data are insufficient to assign a listed risk flag, and only for files not matched by the secret-bearing file rule.
7. Return the output in the fixed order defined below.

Commands to Prefer

Use read-only commands only.

Preferred commands:

• git rev-parse --show-toplevel
• git rev-parse --abbrev-ref HEAD
• git status --short
• git diff --stat
• git diff --cached --stat

Use targeted diff inspection only under the deep diff inspection cap, and only for files not matched by the secret-bearing file rule.

Fail-Fast Rule

If the target path is not inside a git repository:

• stop immediately
• report that the path is not a git repository
• do not continue with generic filesystem analysis

Branch Handling

Branch name is optional metadata only. If branch name is available from a preferred read-only command, include it in Repo state. If HEAD is unavailable or branch name lookup fails in an otherwise valid repo, omit branch metadata without error. Do not give branch advice.

Deep Diff Inspection Cap

Deep diff inspection is optional and must remain narrow.