Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Commit Scope Proof — Staged Git Receipt

    1

    Check that staged files match your intended change. Spot missing or extra paths before asking an agent to describe the commit.

    Free

    1 useSecurity scanned
    Commit Scope Proof — Staged Git Receipt

    Commit Scope Proof — Staged Git Receipt

    Example session with this skill installed

    Actual synthetic local task: the intent is “Add the greeting note”. Expected paths are notes.txt and absent.txt; the disposable repository currently stages notes.txt and extra.txt.

    Check the exact staged scope. Show the missing/extra paths and fingerprint, then tell the owner what to resolve. Do not stage, unstage or commit anything.

    • Read your context and instructions
    • Compiled the commit scope proof

    Staged scope: REVISE

    Intent: Add the greeting note. This result comes from an actual synthetic local helper run.

    PathExpected?Staged?Finding
    notes.txtYesYesIn scope
    absent.txtYesNoMissing
    extra.txtNoYesUnexpected

    The repository has no initial commit yet. Both staged entries are additions with mode 100644. Index, HEAD and reference bytes were unchanged by this check.

    Next action: ask the owner whether to supply/stage the missing file, remove the extra file from staging or deliberately revise the intended scope. The helper made none of those changes. Rerun after that decision; do not describe this receipt as a matching commit scope.

    Fingerprint for this observation
    sha256:cb6d8a041d840b73aaf943e86a1eaa36e7e7b4b57b5bdc2e5fb41df057fc7cc8

    Retain the complete JSON receipt for the object identities. A later staging change can invalidate this snapshot. This says nothing about the code's behaviour or the correctness of a proposed commit message.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    You have several changes in one working tree. The agent is about to write a commit message—but is the staged set the change you meant to commit?

    Give Commit Scope Proof the selected repository, your intent and the paths you expect. Its local helper compares that list with Git's index and shows what is missing or unexpectedly staged. It does not change your staging to make the result pass.

    A scope check you can repeat

    The receipt records staged paths, file modes and Git object identities. A fingerprint binds it to the observed HEAD and index. Supply that fingerprint again to detect changed staging before relying on the earlier receipt.

    A match returns PASS; missing or extra paths return REVISE with the exact path lists. Conflicts, stale evidence, invalid inputs and sensitive-looking filenames return HOLD with a recovery step. Renames are deletion plus addition, so include both paths.

    The ZIP includes the Python helper and a disposable Git quickstart. It needs Python 3.10+, Git 2.30+ and approved local file/terminal access. Local execution was checked on macOS with Python 3.12 and 3.14; other operating systems, minimum-version execution and third-party on-demand retrieval are unverified.

    This checks scope, not code behaviour or commit-message meaning. It reads Git metadata, not file bodies; the filename warning is not a secret scan. The observation does not lock Git, so recheck immediately before use.

    Start with the files the change should include—not whatever happens to be staged.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Code Quality & Review.

    PASS means the exact expected/staged path sets match with no detected hold condition. It does not validate code behaviour, message meaning or submodule contents.
    The fingerprint binds HEAD and raw index identities, not unstaged/untracked edits or a future commit. It is not an atomic Git lock; transient or later concurrent changes can invalidate it.
    Filename-only sensitive-path heuristics may flag harmless examples. No file bodies or secret values are inspected and no secret-free certification is provided.
    Renames are deletion plus addition. The manifest needs a nonempty unique expected path list; absolute/dot-segment/backslash/control-character paths are unsupported.
    The helper changes no index, HEAD, configuration or source files and performs no stage, commit, reset, stash, push, package installation or network call.
    Local proof used macOS Python 3.12.14/3.14.3 and Apple Git 2.50.1. Minimum Python/Git versions, Windows/Linux and third-party Agensi helper retrieval remain unverified.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 25 days ago

    • Free with an Agensi account

    Software
    Python 3.10+Git 2.30+Local Git worktreeTerminal access

    Permissions

    Terminal / Shell
    Read Files

    Read explicitly selected local Git metadata Run bundled Python and fixed read-only Git commands Read the user's explicit scope manifest No write, network, credentials or account connection required. The disposable quickstart creates only its explicit synthetic fixture; normal checks are read-only.

    Listed27 days ago
    Updated25 days ago

    What's inside

    Frequently Asked Questions

    No. The helper only observes raw metadata and compares the explicit expected path set.

    No. PASS means scope matches with no detected hold condition; semantic and behavioral review remain separate.

    As deletion plus addition. Include both paths in expected_paths.

    Supply the prior fingerprint to detect stale state. After an intentional owner change, issue a fresh receipt without the prior fingerprint and retain the old one as stale.

    No. It holds on sensitive-looking staged filenames before any file-body inspection and may flag harmless examples.

    New in Code Quality & Review

    Free