More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    ReleaseNote Proof — Git Change Trace

    1

    Reconcile release notes against real Git changes and tests before a release.

    Free

    Security scanned
    ReleaseNote Proof — Git Change Trace

    ReleaseNote Proof — Git Change Trace

    Example session with this skill installed

    Run ReleaseNote Proof — Git Change Trace as an evidence-first preflight. This is a representative, hypothetical test case: The draft says “CSV exports fixed” but the release range only changes CSS and documentation. The materials I have available are: Git commit range or PR list; draft release notes; test and migration evidence. Tell me what is evidenced, what is missing, which claims must be held, the exact corrections, and a clean verification plan. Do not claim you opened a file or performed a live run unless one is actually supplied.

    • Read your context and instructions
    • Compiled the releasenote proof

    REPRESENTATIVE EXAMPLE — NOT A LIVE RUN

    PREFLIGHT: HOLD / VERIFY BEFORE ACTING. Task: Reconcile release notes against real Git changes and tests before a release.
    Scenario supplied by buyer: The draft says “CSV exports fixed” but the release range only changes CSS and documentation.

    1. MATERIAL FINDING (HIGH): No export-related diff or test was supplied. The case describes a potential issue; no underlying account, file or production service has been accessed by this illustrative demo.

    2. TRACEABILITY MATRIX

    • Claimed behavior: The draft says “CSV exports fixed” but the release range only changes CSS and documentation.
    • Critical evidence sources: Git commit range or PR list, draft release notes, test and migration evidence.
    • Status: NOT VERIFIED from primary artifacts in this example. A real invocation must attach the files or authorize a read-only source inspection and record exact references.
    1. CHECKS THE SKILL WILL RUN
    • Map each claimed feature or fix to a commit, PR, or changed file rather than a plausible narrative.
    • Compare the release window to the previous tag; flag commits outside the intended interval.
    • Detect rollback, revert, breaking API, migration, and configuration changes omitted from the notes.
    • Separate customer-facing behavior from internal refactoring and speculative impact.
    • Generate concise notes plus an appendix of unresolved claims and verification commands.
    1. CORRECTION TO PROPOSE
      Move the fix claim to UNVERIFIED and request the actual PR; keep the confirmed visual changes. Do not present this as implemented until the seller/developer actually applies the change and reviews the result.

    2. REPRODUCTION / ACCEPTANCE TEST
      Inspect the diff and run the CSV export regression test before restoring the claim. Capture the before/after witness (paths, commands, timestamp, observed outcome), distinguish a script signal from a working end-to-end product, and do not invent a PASS.

    3. SCOPE LIMIT
      Cannot prove runtime behavior from commit messages alone.

    Final handoff: a clear evidence-linked issue list, copy-ready proposed changes where appropriate, a prioritized checklist, and a statement of exactly which tests were and were not run.

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

    About this skill

    ReleaseNote Proof — Git Change Trace

    Reconcile release notes against real Git changes and tests before a release.

    What you receive

    • A ready-to-install skill with a repeatable, evidence-first procedure.
    • A source-to-claim discrepancy matrix, severity tags and specific corrective actions.
    • A clearly separated verification checklist and unknowns register.
    • A representative worked example; it is not passed off as a live customer run.

    Example issue

    The draft says “CSV exports fixed” but the release range only changes CSS and documentation.

    Trust boundary

    Cannot prove runtime behavior from commit messages alone.

    No paid API subscription is bundled. The agent can inspect materials supplied by the buyer in its supported environment. Access to private services is never presumed.

    Cannot prove runtime behavior from commit messages alone.

    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 any payment.

    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

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 8 days ago

    • Free with an Agensi account

    Permissions

    File Scopes

    Buyer-provided
    local
    files
    (read-only)

    No production changes or account access without owner authorization.

    Listed8 days ago

    What's inside

    Frequently Asked Questions

    No. Supply files or authorize a suitable read-only connection. Missing evidence is marked unverified.

    No, they illustrate a representative workflow; the delivered skill uses your actual materials.

    New in Technical Documentation