Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Bug Reproduction Kit Builder for AI Coding Agents

    2

    Turn vague bug reports into structured reproduction kits, diagnostic plans, and precise AI coding prompts.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Bug Reproduction Kit Builder for AI Coding Agents

    Bug Reproduction Kit Builder for AI Coding Agents

    Example session with this skill installed

    Turn this vague bug report into a complete developer-ready reproduction kit and AI coding agent prompt:

    “Some users report that the dashboard is blank after they log in. It does not happen for everyone.”

    Assume this is a SaaS web app. Include severity, missing information, reproduction hypotheses, environment matrix, step-by-step reproduction paths, safe evidence to collect, logging plan, likely root causes, test plan, fix verification checklist, and regression prevention plan.

    • Read your context and instructions
    • Compiled the bug reproduction kit

    === BUG REPRODUCTION KIT ===

    Bug title
    Blank dashboard after login for some users

    Original report
    “Some users report that the dashboard is blank after they log in. It does not happen for everyone.”

    Bug category
    Frontend UI bug, authentication/session bug, permissions bug, data loading bug, intermittent or segment-specific bug

    Severity
    High

    Reason
    The dashboard is a core post-login experience. If users cannot see it, they may be blocked from using the product.

    Priority
    P1

    Affected area
    Post-login dashboard, dashboard API calls, authentication state, user permissions, frontend rendering, empty states

    Known information

    • The dashboard appears blank after login.
    • The issue affects some users, not all users.
    • The issue happens after authentication.
    • The affected user segment is not yet known.

    Missing information

    • Which roles are affected?
    • Which plans are affected?
    • Which browsers/devices are affected?
    • Is the page completely white or is the dashboard shell visible?
    • Are there console errors?
    • Are dashboard API requests returning 401, 403, 500, or empty data?
    • Did this start after a recent deployment?
    • Does refreshing the page fix it?
    • Are feature flags or experiments involved?

    Expected behavior
    After login, users should see the dashboard shell, navigation, widgets, loading states if needed, and either real data or a helpful empty state.

    Actual behavior
    Some users see a blank dashboard after login.

    Reproduction hypotheses

    1. A frontend render error occurs when dashboard data contains null or unexpected fields.
      Confidence: High

    2. A permissions mismatch causes the dashboard API to return 403 for certain roles, and the frontend does not show an error state.
      Confidence: Medium to high

    3. A feature flag or plan configuration hides all dashboard widgets and leaves no empty state.
      Confidence: Medium

    4. A stale or expired session causes dashboard data requests to fail immediately after login.
      Confidence: Medium

    5. Older migrated accounts are missing required dashboard data.
      Confidence: Medium

    Environment matrix

    • Environment: production, staging
    • User role: owner, admin, member, viewer
    • Account plan: free, paid, enterprise
    • Account age: new account, older migrated account
    • Browser: Chrome, Safari, Firefox, Edge
    • Device: desktop, tablet, mobile
    • Auth state: fresh login, refreshed session, expired session
    • Feature flags: dashboard redesign enabled/disabled
    • Data state: no projects, many projects, missing profile data

    Primary reproduction path

    1. Open staging with a test account matching an affected user segment.
    2. Log out fully and clear session storage/cookies if safe.
    3. Log in with the test account.
    4. Observe whether the dashboard shell appears.
    5. Open browser developer tools.
    6. Check console errors.
    7. Check network requests for dashboard APIs.
    8. Record response statuses and sanitized response shapes.
    9. Repeat with owner, admin, member, and viewer roles.
    10. Repeat with a new account, empty account, and older migrated account.

    Evidence to collect

    • Affected user role and plan
    • Browser, device, and OS
    • Timestamp
    • Screenshot or screen recording
    • Console errors with secrets removed
    • Network status codes for dashboard API requests
    • Request ID for failed API calls
    • Sanitized response shape
    • Recent deployment or feature flag changes
    • Whether refresh fixes the issue

    Logging plan
    Add safe logging around dashboard API requests, auth middleware, and frontend error boundaries.

    Log

    • request ID
    • hashed user ID
    • user role
    • plan type
    • route name
    • response status
    • sanitized error code
    • feature flag state
    • timestamp

    Do not log
    passwords, raw tokens, cookies, API keys, private user content, or unnecessary personal data.

    Likely root causes

    1. Unhandled null or unexpected dashboard data causing a frontend crash
    2. Permission or role mismatch causing API failure
    3. Missing empty state for users with no dashboard records
    4. Feature flag combination hiding all widgets
    5. Migration issue affecting older accounts
    6. Session refresh issue after login

    Test plan

    Unit tests

    • Dashboard widgets handle null, empty, and partial data.
    • Role and plan visibility rules return expected widget sets.
    • Empty state appears when no dashboard data exists.

    Integration tests

    • Dashboard API returns valid data for owner, admin, member, and viewer roles.
    • Unauthorized users receive safe error responses.
    • Migrated accounts return valid dashboard payloads.

    E2E tests:

    • Login redirects to dashboard successfully.
    • Dashboard renders for each role and plan.
    • Dashboard shows empty state for new accounts.
    • Dashboard shows error state when API fails.
    • Feature flag combinations do not create a blank page.

    AI coding agent prompt
    Investigate a SaaS dashboard bug where some users see a blank dashboard immediately after login. Do not rewrite the dashboard broadly. First inspect dashboard rendering, dashboard API calls, auth/session handling, role and plan permissions, feature flags, empty states, and frontend error boundaries. Identify whether the blank page is caused by frontend render failure, failed API response, missing data, permissions mismatch, migrated account data, or feature flag configuration. Add or describe failing tests for the affected scenario. Make the smallest safe fix. Do not log passwords, raw tokens, cookies, API keys, private user content, or unnecessary personal data. Verify that the dashboard renders for owner, admin, member, viewer, new accounts, empty accounts, and migrated accounts. Return root cause, files changed, fix summary, tests added or run, verification checklist, and remaining risks.

    Fix verification checklist

    • Affected users can log in and see dashboard content or a helpful empty state.
    • No blank dashboard appears.
    • Console has no render-blocking errors.
    • Dashboard API responses are handled safely.
    • 401/403/500 responses show useful error states.
    • New accounts show empty state.
    • Older migrated accounts render correctly.
    • Role permissions remain correct.
    • Feature flag combinations do not hide all content.
    • Regression tests pass.
    • No sensitive data is logged.

    Regression prevention plan

    • Add dashboard smoke test after login.
    • Add role-based dashboard integration tests.
    • Add empty-state tests.
    • Add frontend error boundary monitoring.
    • Add feature flag combination tests.
    • Add migration validation for dashboard-required fields.
    • Add release checklist item for post-login dashboard rendering.

    Risk and safety notes
    Because this bug may involve authentication, permissions, and user-specific data, use sanitized logs, non-production test accounts when possible, and human review before changing access-control logic.

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

    About this skill

    Bug Reproduction Kit Builder helps AI coding agents, developers, QA teams, support teams, and product teams turn vague or incomplete bug reports into clear, developer-ready reproduction packages. It creates structured bug summaries, severity analysis, missing-information checklists, reproduction hypotheses, environment matrices, step-by-step repro plans, safe evidence requests, logging and instrumentation plans, test strategies, AI coding agent debug prompts, fix verification checklists, and regression prevention plans. Ideal for debugging frontend, backend, full-stack, API, authentication, checkout, database, mobile, browser, performance, deployment, and intermittent bugs before attempting a fix.

    This skill creates structured bug reproduction plans, diagnostic strategies, QA test plans, regression checklists, and AI coding agent prompts, but it does not guarantee that a bug will be reproduced, fixed, deployed, or permanently prevented. Complex issues such as intermittent bugs, production-only failures, race conditions, third-party integration errors, security-sensitive bugs, payment issues, and data-loss scenarios may require repository access, logs, monitoring tools, staging environments, automated tests, or human expert review.

    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 5 months ago

    Permissions

    Browser
    Write Files
    Read Files

    File Scopes

    *.md
    *.txt
    *.log
    *.json
    *.yaml
    *.yml
    src/**
    app/**
    components/**
    server/**
    pages/**
    tests/**
    api/**
    __tests__/**
    cypress/**
    playwright/**

    This skill uses file access to read user-provided bug reports, QA notes, sanitized logs, issue descriptions, code snippets, configuration examples, and technical documentation. It uses write access to create structured Markdown/text outputs such as reproduction kits, AI coding agent debug prompts, QA test plans, regression checklists, bug intake forms, and SKILL.md files. Terminal access is only needed if the agent is expected to inspect repositories, run tests, or validate debugging workflows. Normal use does not require browser, network access, or environment variables.

    Listed5 months ago
    Updated1 month ago

    What's inside

    Frequently Asked Questions

    This skill acts as a bridge between vague user reports and actionable code fixes. It automates the creation of environment matrices, instrumentation plans, and precise prompts specifically designed to guide AI coding agents through the debugging process without manual guesswork.

    The Bug Reproduction Kit Builder is agent-agnostic and designed to work with all major AI coding assistants (such as GitHub Copilot, Cursor, or Replit Agent) by providing them with structured context and diagnostic instructions they can actually follow.

    You will receive the full skill configuration, including the logic for generating reproduction hypotheses, severity analysis frameworks, and the specialized prompt templates used to brief your AI coding agents.

    No complex installation is required; once purchased, you can integrate the skill into your existing agentic workflow or use it as a standalone utility to process bug reports from Jira, GitHub Issues, or Slack.

    While most bugs are straightforward, this skill includes a specialized "Intermittent Bug" module that generates logging and instrumentation plans specifically designed to capture the state of non-deterministic or race-condition errors.

    Yes, buyers receive lifetime access to all future updates, which include refined diagnostic strategies and updated prompt templates optimized for the latest versions of LLMs.

    New in Testing & Debugging