Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Post-Implementation Jira Update

    1

    Keeps Jira an honest record of real progress — posts evidence-backed comments at defined points, and only moves a ticket to Done when a real merge actually happened.

    $4.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Post-Implementation Jira Update

    Post-Implementation Jira Update

    Example session with this skill installed

    PR #73 for PROJ-110 just got merged, CI was green — update the ticket.

    • Read your context and instructions
    • Compiled the post-implementation jira update

    Summary

    Posted merge evidence as a comment and moved the ticket to Done — but only because the merge is confirmed real and every acceptance criterion is complete.

    CheckResult
    Merge confirmedYes — commit 8287c80, PR #73
    Acceptance criteriaComplete
    Comment postedYes, with merge link + evidence
    Status transitionIn Progress → Done
    {
  "issueKey": "PROJ-110",
  "trigger": "post-merge",
  "mergeConfirmation": { "prUrl": "https://github.com/your-org/your-repo/pull/73", "mergeCommitSha": "8287c80" },
  "commentPosted": true,
  "statusTransition": { "attempted": true, "from": "In Progress", "to": "Done", "reason": "acceptanceCriteriaReport.overallStatus is complete and mergeConfirmation is present" },
  "descriptionOrAcModified": false
}

    Next steps

    • Nothing — the ticket's Jira state now matches reality. descriptionOrAcModified stays false: the original requirement was never touched, only reported on.

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

    About this skill

    A ticket's Jira state should reflect what actually happened — never an optimistic guess, and never a rewrite of the original requirement. This skill updates Jira at four distinct, real points in a ticket's lifecycle: local completion (before anything is pushed), PR creation, PR merge, or a blocked state — each with its own comment built from real evidence, never a fabricated check result.

    It never edits the original ticket description or acceptance criteria — only adds comments, and transitions status by a strict rule: a ticket only moves to Done after a real, confirmed merge (not just a PR being opened) and only when acceptance criteria are actually complete. A blocked ticket never reaches Done, no matter how much code was written.

    Part of the Ticket-to-Shipped workflow: 10 skills covering the full requirement-to-shipped-code lifecycle. Works standalone too.

    Requires a Jira MCP integration already connected and authenticated. Assumes your project's real, observed status-transition history (check it first) — its default mapping assumes a simple To Do → In Progress → Done flow without a separate In Review status; adapt if your project differs. Won't transition to Done without explicit merge confirmation — a PR merely being open or created is never treated as proof of a merge.

    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

    Money-back guarantee

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

    Trust & safety

    Security scan

    Security scan passed today

    Requires

    Jira (E.G. Atlassian Integration) MCP

    Permissions

    Network Access

    Only ever adds comments and transitions status — never edits the ticket's original description or acceptance criteria.

    Listedtoday

    What's inside

    Frequently Asked Questions

    Unlike generic prompts that assume a task is complete once code is written, this skill requires deterministic evidence—such as PR merge confirmation and passed acceptance criteria—before updating a ticket's status.

    This skill requires the Jira Model Context Protocol (MCP) tools for API access and integrates with common intake and verification workflow objects to process implementation data.

    No, the skill is designed with integrity protection that ensures the original ticket descriptions and acceptance criteria remain untouched; it only adds evidence-backed comments and updates status transitions.

    It triggers and updates at four critical stages: local completion, PR creation, successful PR merge, and whenever a blockage or failure is detected during verification.

    The skill will document the failure in a detailed Jira comment and refuse to transition the ticket to 'Done,' ensuring project managers are alerted to the specific blocker immediately.

    You receive the production-ready skill logic, documentation for configuring the required Jira MCP tools, and the workflow definitions for connecting it to your intake and verification stages.