What problem does it solve? Agents and developers often make many edits in a row without committing, leaving work at risk of being lost if a session ends or a subagent gets stuck. This Skill watches the live uncommitted-file count after every edit-shaped tool call and issues an imperative commit command once a threshold is crossed, escalating to an at-risk report when commands go unanswered. ## Core Features & Use Cases - PostToolUse commit nudge: After every Write/Edit/MultiEdit/NotebookEdit call, runs git status --porcelain and emits an additionalContext command to commit using Conventional Commits once the count crosses a configurable threshold (default 5). - Debounced escalation: A re-arming ratchet fires only on new highs, and after 3 unanswered commands the message escalates to a WIP-commit warning and the project is recorded as at risk. - Parent-facing risk report: scripts/ensure_committed.py lists projects, sessions, and how long work has been uncommitted, so a parent agent can take over, commit, or stop a stuck subagent. - Use Case: A subagent has been editing files for a long time without landing anything; run ensure_committed.py to see which project and session is at risk while there is still time to recover the work. ## Quick Start Ask the agent to check whether any project has unanswered commit reminders by running the ensure_committed.py script and then commit or take over any at-risk work it names.