Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    QA Bug Ticket Standardizer

    1

    Converts vague user complaints and error logs into professional, developer-ready Jira bug tickets.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    QA Bug Ticket Standardizer

    QA Bug Ticket Standardizer

    Example session with this skill installed

    • Raw Complaint / Feedback: "The checkout is completely broken! I tried buying the annual plan with a promo code on my phone and the pay button just spins forever." - Application / Module Context: B2B SaaS Billing Portal (Stripe Checkout integration) - Known Environment / Logs (Optional): Reported by a customer on an iPhone using Safari. Production environment.
    • Read your context and instructions
    • Compiled the qa bug ticket

    [BUG] [Checkout / Stripe Payment]: Pay button hangs indefinitely (infinite spinner) when purchasing annual plan with promo code on iOS Safari

    Classification & Triage

    • Issue Type: Bug

    Severity: Critical - Blocks revenue-generating checkout flow on production for a mobile Safari user; no workaround confirmed yet (desktop retry untested).

    • Priority: P1
    • Component/Module: B2B SaaS Billing Portal / Stripe Checkout integration

    Description
    A customer attempting to purchase an annual plan with a promo code on an iPhone (Safari) reports that the "Pay" button enters a perpetual loading state and the transaction never completes or returns an error. This indicates a likely unresolved or failed async request during payment confirmation, with no timeout or error handling surfaced to the user. Impact: lost conversions and potential duplicate charges if the user retries. The report only confirms one user and one device, so scope is unknown.

    Environment Matrix

    • Device / Platform: iPhone (mobile) - [To Verify - e.g., iPhone 14 / 15]
    • OS & Version: [To Verify - e.g., iOS 17.4]
    • Browser / App Version: Safari - [To Verify - version / in-app browser vs. standalone Safari]
    • Environment: Production
    • User Account / Role: [To Verify - e.g., new customer vs. existing account, org admin / billing role]

    Steps to Reproduce
    1.

    Preconditions: User is logged into the Billing Portal on an iPhone using Safari; the annual plan and a valid promo code are available. [To Verify - promo code value, type, and validity]
    2. Open the Billing Portal and navigate to the plans/pricing page. [Inferred]
    3. Select the Annual plan and proceed to Stripe Checkout. [Inferred]
    4. Enter the promo code in the promo/discount field and apply it. [Inferred]
    5. Enter payment details. [Inferred]
    6. Tap the Pay button. Bug triggers here.

    Expected Result
    After tapping Pay, the payment is processed within a few seconds. The user is redirected to a success/confirmation page with the discounted annual total charged, or shown a clear error message if payment fails.

    Actual Result
    The Pay button displays a spinner indefinitely. No success confirmation, redirect, or error message appears, and the user cannot tell whether the payment was submitted or charged.

    Diagnostic Checklist & Probable Root Cause (For QA/Dev)

    • Probable Area of Failure:
      • Promo code / coupon handling (e.g., discount application producing an invalid amount or session state, or a 100%-off / zero-amount edge case)
      • Stripe Checkout session or PaymentIntent confirmation request hanging or never resolving (missing webhook handling or unhandled promise on the frontend)
      • iOS Safari-specific behavior (e.g., Intelligent Tracking Prevention blocking third-party cookies, 3DS/redirect popup blocked, payment-sheet or Apple Pay interaction issue)
    • Info Needed to Verify:
      • Stripe Dashboard logs for the customer's session/PaymentIntent (status, errors, whether a charge or incomplete intent was created)
      • Browser console logs and HAR/network capture from iOS Safari (via Mac Web Inspector) showing the stalled request
      • Backend/server logs and webhook delivery logs around the time of the attempt
      • Screen recording or screenshot of the stuck state, plus exact timestamp and customer ID
      • Repro without the promo code (annual plan only) on the same device
      • Repro with the promo code on desktop Chrome and on another iOS Safari version
      • Repro with a monthly plan + promo code to isolate plan vs. promo cause
      • Check whether the customer was double-charged or has a pending/incomplete subscription

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

    About this skill

    Technical debt often starts with poorly documented bugs. This skill functions as a Senior QA Technical Triage Specialist, converting vague customer complaints and raw error notices into standardized, developer-ready Jira tickets. It eliminates the back-and-forth between support and engineering by enforcing a strict documentation structure that includes inferred reproduction steps and severity classifications.

    What it does

    • Standardizes tickets by converting raw text into Jira-compatible Markdown with professional technical summaries.
    • Deduces reproduction steps using logical sequences, clearly marking extrapolated actions as inferred for developer verification.
    • Extracts environment data to capture OS, browser, and device versions, providing placeholders for missing critical parameters.
    • Performs objective triage by assigning severity and priority levels based on business impact and the existence of workarounds.
    • Suggests root causes by identifying probable areas of failure, such as API timeouts or frontend state issues, to accelerate debugging.

    How it works

    1. Input the raw complaint or feedback text along with any known application context or logs.
    2. The agent analyzes the text to deduce the user journey and environmental conditions.
    3. It generates a formatted bug report including classification, reproduction steps, and diagnostic checklists.

    Frameworks & tools

    This skill is framework-agnostic and produces standard Jira Markdown. It is suitable for any development team using issue trackers like Jira, Linear, or GitHub Issues.

    Why this beats prompting it yourself

    Writing bug reports manually is time-consuming and prone to missing environmental context. This skill uses specific QA logic to infer missing steps and objective severity criteria that a generic prompt often overlooks, ensuring tickets are immediately actionable for developers.

    Use cases

    • Customer Support Triage to turn vague tickets into technical bug reports.
    • QA Smoke Testing for rapid documentation of defects found during manual passes.
    • Log Analysis to translate raw stack traces into readable issue descriptions.
    • Junior Dev Guidance to teach team members what a "good" bug report looks like.

    Known limitations

    Does not integrate directly with Jira APIs; it generates Markdown for copy-pasting. Accuracy of inferred steps depends on the detail provided in the raw complaint.

    Produces Markdown only, no direct API integration with Jira. Inferred steps require manual verification. Effectiveness scales with the quality of the initial raw complaint context.

    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 1 month ago

    Permissions

    No special permissions declared or detected

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    The skill acts as a bridge between non-technical feedback and engineering, automatically structuring vague complaints into professional Jira tickets with clear reproduction steps and severity levels. This eliminates the manual back-and-forth typically required for developers to understand a bug report.

    This skill is framework-agnostic and generates standardized Markdown, making it compatible with Jira, Linear, GitHub Issues, and Trello. It works across any AI agent platform that supports text-based processing and prompt execution.

    Yes, the skill is designed to parse raw logs and stack traces, converting complex technical errors into a readable 'Root Cause Analysis' section within the generated bug ticket.

    Setup is near-instant; once you add the skill to your agent, you simply provide the raw user complaint. No API integrations or complex configurations are required since it generates ready-to-paste Markdown content.

    While the skill is highly effective at inferring missing steps based on technical logic, it explicitly flags any 'extrapolated' actions as inferred so your developers know exactly what has been verified versus what is a logical assumption.

    Your purchase includes the specialized QA logic and ticket formatting templates. As part of our marketplace standard, you will receive notifications for any logic optimizations or formatting updates released by the developer.

    New in Agents & Orchestration