Release Proof Notes — Check the Claims Behind Your Changelog

    1

    Draft release notes with a private claim-to-code ledger. Check the final Git range and keep deployment uncertainty explicit.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Release Proof Notes — Check the Claims Behind Your Changelog

    Example session with this skill installed

    Review a synthetic history where an export feature was added and fully reverted. Collect the selected range, compare the final changed-file list and explain which public claim should be held until the final diff is inspected. Do not create or publish a release.

    • Read your context and instructions
    • Compiled the release proof notes

    Synthetic add-then-revert history

    This complete captured collector report comes from a temporary synthetic Git repository. It is not a production release or evidence of deployment.

    {
  "status": "COLLECTED",
  "base": "76a9450a5bfb3639bb76aa2240c37dd3b2a69857",
  "head": "74c2b8d4ed26473baa161ab28739dd3143a5a82f",
  "commit_count": 2,
  "commits": [
    {
      "sha": "d356c7de574ae322de83bc451c1dd126fdf6490c",
      "subject": "feat: add export",
      "body": "feat: add export",
      "parents": [
        "76a9450a5bfb3639bb76aa2240c37dd3b2a69857"
      ],
      "revert_references": []
    },
    {
      "sha": "74c2b8d4ed26473baa161ab28739dd3143a5a82f",
      "subject": "Revert \"feat: add export\"",
      "body": "Revert \"feat: add export\"\n\nThis reverts commit d356c7de574ae322de83bc451c1dd126fdf6490c.",
      "parents": [
        "d356c7de574ae322de83bc451c1dd126fdf6490c"
      ],
      "revert_references": [
        "d356c7de574ae322de83bc451c1dd126fdf6490c"
      ]
    }
  ],
  "final_changed_files": [],
  "working_tree_changes_excluded": false,
  "deployment": "UNKNOWN",
  "limits": [
    "Messages are not semantic proof.",
    "Final file changes are not deployment evidence.",
    "Only standard revert messages are recognized.",
    "Untracked files are outside the committed range."
  ],
  "evidence_sha256": "202424c1d8a7229b0a426492782e3241acf9f40ad6be117af4513097b60b1388"
}

    Worked claim review

    Proposed claimObserved evidenceDisposition
    Export is now availableExport was added and then reverted; the final changed-file list is emptyHOLD
    This range changed the delivered productNo final changed files are collectedNot supported by this report
    Deployment completedDeployment is UNKNOWNDo not publish this claim

    Customer-facing draft

    No new export feature is announced from this range. Confirm the final diff and deployment evidence before publishing a release note. Exit 0 means evidence collection succeeded, not that any release claim was approved.

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

    About this skill

    A feature can be merged and then reverted. A performance commit can lack a benchmark. A code change can still be behind a flag. A polished changelog should not quietly turn those facts into “available now.”

    Release Proof Notes gives your agent a bounded local evidence collector and a review workflow for public release claims. Select the repository, base and head; collect immutable commit IDs, messages, standard revert references and final changed paths. Then inspect the relevant code/diffs and draft the customer wording alongside a private evidence ledger.

    You receive

    • A release-note draft for the stated audience and range.
    • Per-claim sources, implementation/deployment evidence and review disposition.
    • Held or reworded claims where evidence is missing.
    • Breaking-change/migration unknowns without invented instructions.
    • A local collector using Python's standard library and Git, with no fetch, write or release operation.

    The collector defaults to 200 commits and refuses silent truncation. It flags excluded tracked working-tree changes and leaves deployment UNKNOWN. It recognizes standard revert messages; it does not prove semantic reversions, feature availability or performance. Exit 0 means collection succeeded, not that the release is approved.

    For basic PR lists, GitHub's built-in release notes may be sufficient. This skill focuses on checking the claims before you publish them; it is not a replacement for release tooling or deployment evidence.

    Scope and limitations

    Needs access to the bundled script and a Git repository for executable collection. A supplied-log review is possible but must state its weaker evidence. No automatic tags, commits, pushes, release creation, production access or security-disclosure approval is included. Keep the source ledger private: commit messages can contain confidential data. Other agents and Agensi's current script delivery have not been independently validated.

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scanned

    Verified clean today

    • Passed all security checks, Safe to install

    Requires

    Python 3.10+
    Git
    Terminal / Shell
    Local repository and bundled collector access

    Listedtoday

    What's inside

    Frequently Asked Questions