Bug Report Issue Triage Assistant

    1

    Transform raw bug reports and logs into structured, evidence-based engineering tickets and triage assessments.

    Free

    0 installsSecurity scanned

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    Bug Report Issue Triage Assistant

    Example session with this skill installed

    Triage this: User says the 'Save' button on the profile page didn't work. They tried twice on Chrome. No error message shown. Here is the log: [2023-10-01 10:00:05] ERROR: 500 at /api/v1/profile.

    • Read your context and instructions
    • Compiled the bug report issue
    • Generated the document

    The report has been analyzed. While the user impact is high, the reproduction steps are partially described and require more context for a full fix.

    Executive Triage

    • Issue Title: Profile Save Failure (Internal Server Error 500)
    • One-Line Diagnosis: API endpoint /api/v1/profile returned a 500 error during a profile update attempt.
    • Triage Status: NEEDS MORE INFORMATION
    • Severity: S2 High (Core functionality blocked)
    • Priority: P1 Urgent
    • Confidence: Medium

    Evidence Summary

    • Confirmed Facts: System log shows 500 Internal Server Error at /api/v1/profile.
    • Reported Behavior: 'Save' button non-functional on profile page.
    • Key Evidence: Timestamp 2023-10-01 10:00:05.
    • Missing Information: Request payload, user ID, and full stack trace from the server side.

    Developer-Ready Ticket

    • Title: [BUG] 500 Error on /api/v1/profile Save Action
    • Context: User attempting to update profile settings via web UI.
    • Environment: Chrome (version not provided).
    • Steps to Reproduce:
      1. Navigate to the profile settings page.
      2. Click the 'Save' button.
      3. Observe UI behavior (reported as no error message shown).
    • Expected Result: Profile updates successfully; API returns 200 OK.
    • Actual Result: API returns 500 Internal Server Error.
    • Suspected Component: Backend API (/api/v1/profile).
    • Acceptance Criteria:
      • The /api/v1/profile endpoint returns 200 OK upon valid save requests.
      • UI displays an error state if the API fails, rather than failing silently.

    Issue Quality

    • Score: 45/100
    • Gaps: Missing request/response payloads and specific browser version.

    Next steps

    1. Check server-side logs for the full stack trace corresponding to timestamp 10:00:05.
    2. Request the specific account ID or email from the reporter to check for data-specific edge cases.
    3. Verify if this occurs on other browsers or is isolated to Chrome.

    bug-report-issue-triage-assistant.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    About this skill

    The Problem

    Developers often receive vague bug reports, incomplete logs, and subjective user complaints. Manually verifying these issues, chasing missing information, and assessing technical severity consumes hours of engineering time better spent on fixes.

    What It Does Analyzes raw bug reports, stack traces, and logs to extract confirmed facts versus reporter hypotheses. Calculates a 0–100 Issue Quality Score based on problem definition, environment context, and available evidence. Determines technical severity (S1–S4) using an evidence-gate system that separates impact from priority. Generates implementation-ready engineering tickets with observable acceptance criteria and reproduction steps. Identifies specific missing information that is currently preventing successful triage. Why This Beats Prompting It Yourself

    Standard prompts often hallucinate missing reproduction steps or invent root causes to be helpful. This skill uses strict evidence-first logic that explicitly labels unknown information as NOT PROVIDED, helping engineers avoid chasing unsupported assumptions or treating a reported issue as independently verified.

    Use Cases Converting messy customer support tickets into structured Jira or GitHub issues. Auditing existing backlogs to identify tickets that lack sufficient evidence for development. Performing rapid security triage on incoming reports to flag potential authentication or data exposure risks. Comparing multiple reports to detect likely duplicates or related regressions. Known Limitations

    This skill does not independently execute code or verify bugs in a live environment. It relies entirely on the text, logs, and artifacts provided in the input.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    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

    Free forever

    No account required to browse

    Trust & safety

    Security scanned

    Verified clean 3 days ago

    • Free to download with an account

    Listed3 days ago

    What's inside

    Frequently Asked Questions