What problem does it solve? When you return to a branch after days away or an agent edits many files, it is hard to know exactly what is sitting uncommitted in your working tree. This Skill reads the actual staged, unstaged, and untracked changes and explains what will behave differently, so you can decide whether the work is finished and ready to commit. ## Core Features & Use Cases - Complete worktree collection: A script gathers staged diffs, unstaged diffs, untracked file contents, hidden assume-unchanged paths, and submodule pointers in one call, so nothing is silently missed. - Behavior-first explanation: Changes are grouped by what they do rather than by file path, each carried down to an observable consequence such as a different return value, query, or rendered output. - Completeness checking: For every changed signature, name, or config key, callers are grepped and checked against the diff to surface half-shipped changes, plus accidental content like debug prints and leftover .only tests. - Use Case: You come back to a feature branch after the weekend and ask what is uncommitted; the Skill produces a structured report covering scope, intent, behavioral changes, call-flow deltas, loose ends, and commit coherence. ## Quick Start Ask the assistant to explain everything uncommitted in my working tree before I commit it.
