Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Repo-to-Release Doctor | CI to Live Verification

    1

    Green CI, broken deployment? Trace the exact commit, build artifact bytes and live HTTPS release readback.

    $17

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Repo-to-Release Doctor | CI to Live Verification

    Repo-to-Release Doctor | CI to Live Verification

    Example session with this skill installed

    My GitHub Actions run is green but production reports an old build. Given manifest.json, dist/app.tar.gz, run 1234567890 and a release readback endpoint, determine the first mismatch.

    • Read your context and instructions
    • Compiled the repo-to-release doctor

    Verdict: FAIL — RUNTIME_SHA_MATCH: expected commit aaaa..., observed bbbb...; local artifact SHA-256 and GitHub CI match. Scope: one live HTTPS endpoint. Suggested action: inspect deployment promotion and image/reference mapping. No changes made.

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

    About this skill

    Your build passed. But is the release you shipped actually running?

    Repo-to-Release Doctor is a read-only, SHA-bound release diagnostic for GitHub Actions, a local build artifact and a single live HTTPS endpoint. Its bundled Python 3 utility compares expected commit, real GitHub Actions run, exact artifact SHA-256, intended deployment revision, and runtime readback. It produces a structured PASS / FAIL / INDETERMINATE result with JSON and readable Markdown.

    What buyers get

    • Reproducible evidence chain: GitHub CI → artifact digest → deployed revision → HTTPS runtime.
    • A mismatch report that identifies exactly which boundary disagrees.
    • Separate imported evidence from independently observed data. No invented production-green claims.
    • Read-only, no deployment writes, no subscriptions or additional hosted service required.
    • Python 3 standard-library CLI and example manifest contract included.

    Limits: This does not deploy or fix production automatically. Requires access to your own GitHub Actions run, actual release artifact and a purpose-built readback endpoint for a full live verification. A single runtime endpoint does not attest an entire cluster. The tool is not a hosted MCP server.

    Suitable for Node.js, React, Go, Rust, C++ and other CI-backed stacks because the evidence contract, not the programming language, is what is checked.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.

    A single HTTPS readback observes one endpoint, not all replicas. CI connector requires GitHub CLI authenticated by buyer. No runtime proof from imported claims. Does not deploy, attest signatures, operate a hosted MCP, or test application correctness.

    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

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

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

    Trust & safety

    Security scan

    Security scan passed 11 days ago

    Accounts
    GitHub
    Software
    Python 3.10+
    Optional
    GitHub CLIHTTPS deployment readback endpoint

    Python runs the bundled CLI. A signed-in GitHub CLI enables real CI observation; the HTTPS readback endpoint enables live verification.

    Permissions

    Allowed Hosts

    api.github.com
    buyer-provided explicit HTTPS readback host

    File Scopes

    Read
    manifest
    artifact
    and
    optional
    imported
    readback
    file;
    optionally
    write
    local
    JSON/Markdown
    report

    Read-only. No production deployment or account mutation. Full PASS requires real GitHub CI, actual artifact and live HTTPS readback; imported data alone cannot yield PASS.

    Listed11 days ago

    What's inside

    Frequently Asked Questions

    No, it identifies precisely where actual code, CI, artifact and runtime claims disagree, without risky production mutations.

    No. It validates one readback endpoint and stated evidence boundaries. Cluster-wide coverage requires independent checks of all replicas.

    Yes, in imported/offline contradiction-check mode. It cannot truthfully claim full live PASS unless CI is independently observed.