Run any Skill in Manus with one click

automating-bug-reporting

Stars0

Forks0

UpdatedFebruary 16, 2026 at 16:52

Processes failed test executions, screenshots, and logs to generate comprehensive bug reports and automatically create JIRA tickets. Includes root cause analysis and environment details.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

bhaumikgohel

bhaumikgohel/Antigravity-SKILLS

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

3 files

SKILL.md

readonly

name	automating-bug-reporting
description	Processes failed test executions, screenshots, and logs to generate comprehensive bug reports and automatically create JIRA tickets. Includes root cause analysis and environment details.

Automating Bug Reporting

When to use this skill

When a user provides a "Failed test execution" report, "Screenshot", or "Logs".
When a bug report needs to be generated with "Steps to Reproduce", "Expected/Actual Results", and "Root Cause".
When automatic JIRA ticket creation with "Priority" and "Severity" is required.

Workflow

Artifact Analysis:
- Logs: Parse logs to identify the stack trace, error message, and timestamp.
- Screenshot: Analyze the screenshot to identify visual discrepancies or UI state at failure.
- Execution Report: Identify the specific test case that failed and the environment it ran in.
Report Generation:
- Synthesize findings into a structured bug report.
- Determine Root Cause by correlating log errors with test steps.
- Assess Priority and Severity based on error type (e.g., Crash = Blocker/P0, Typos = Low/P3).
JIRA Automation:
- Format the synthesized data for JIRA API.
- Execute the creation script or provide the JSON payload for manual entry if API is disconnected.

Instructions

1. Data Identification

Tracebacks: Look for keywords like AssertionError, NullPointerException, TimeoutError.
Log Correlation: Match the failure timestamp in logs with the test step execution.

2. Bug Report Template

# [Bug Title]
- **Environment**: [OS, Browser, Version, Environment (Stage/Prod)]
- **Steps to Reproduce**:
  1. ...
  2. ...
- **Expected Result**: ...
- **Actual Result**: ...
- **Root Cause Analysis (RCA)**: [The technical reason why it failed]
- **Priority**: [Critical|High|Medium|Low]
- **Severity**: [S1|S2|S3|S4]

3. Automatic JIRA Creation

Use the provided script in scripts/jira_ticket_helper.py (if configured) or generate the command:

# Example for a hypothetical JIRA CLI or API call
python scripts/jira_ticket_helper.py --title "[Title]" --description "[Body]" --priority "High"

Checklist

Resources

More from this repository

same repository

generating-n8n-workflows

bhaumikgohel/Antigravity-SKILLS

Generates n8n workflow JSON files from user prompts for download and import. Use when user wants to create n8n automation, mentions workflow generation, or needs a .json file for n8n import.

2026-02-200

detecting-duplicate-bugs

bhaumikgohel/Antigravity-SKILLS

Detects duplicate JIRA bugs before creation by comparing new bug summaries against existing issues. Use when QA is logging bugs, mentions potential duplicates, or before creating new JIRA tickets.

2026-02-200

running-smoke-tests

bhaumikgohel/Antigravity-SKILLS

Runs automated smoke tests after deployment to validate critical paths and UI readiness. Use after deployments, before releases, or when verifying environment health.

2026-02-200

validating-ui-content

bhaumikgohel/Antigravity-SKILLS

Validates UI text content for spelling, grammar, formatting, and consistency issues. Use when testing web pages, reviewing UI copy, checking for content errors, or validating labels and messages.

2026-02-200

generating-test-data

bhaumikgohel/Antigravity-SKILLS

Automatically generates valid, invalid, and boundary test data based on field names and validation rules. Use when the user provides field specifications and needs a comprehensive data set for testing forms, APIs, or database constraints.

2026-02-160

mapping-requirements-to-test-cases

bhaumikgohel/Antigravity-SKILLS

Analyzes requirement documents and existing test cases (Excel/JIRA) to identify coverage gaps, duplicates, and missing scenarios. Generates a gap analysis report mapping requirements to test coverage status.

2026-02-160

name	automating-bug-reporting
description	Processes failed test executions, screenshots, and logs to generate comprehensive bug reports and automatically create JIRA tickets. Includes root cause analysis and environment details.

Automating Bug Reporting

When to use this skill

When a user provides a "Failed test execution" report, "Screenshot", or "Logs".
When a bug report needs to be generated with "Steps to Reproduce", "Expected/Actual Results", and "Root Cause".
When automatic JIRA ticket creation with "Priority" and "Severity" is required.

Workflow

Artifact Analysis:
- Logs: Parse logs to identify the stack trace, error message, and timestamp.
- Screenshot: Analyze the screenshot to identify visual discrepancies or UI state at failure.
- Execution Report: Identify the specific test case that failed and the environment it ran in.
Report Generation:
- Synthesize findings into a structured bug report.
- Determine Root Cause by correlating log errors with test steps.
- Assess Priority and Severity based on error type (e.g., Crash = Blocker/P0, Typos = Low/P3).
JIRA Automation:
- Format the synthesized data for JIRA API.
- Execute the creation script or provide the JSON payload for manual entry if API is disconnected.

Instructions

1. Data Identification

Tracebacks: Look for keywords like AssertionError, NullPointerException, TimeoutError.
Log Correlation: Match the failure timestamp in logs with the test step execution.

2. Bug Report Template

# [Bug Title]
- **Environment**: [OS, Browser, Version, Environment (Stage/Prod)]
- **Steps to Reproduce**:
  1. ...
  2. ...
- **Expected Result**: ...
- **Actual Result**: ...
- **Root Cause Analysis (RCA)**: [The technical reason why it failed]
- **Priority**: [Critical|High|Medium|Low]
- **Severity**: [S1|S2|S3|S4]

3. Automatic JIRA Creation

Use the provided script in scripts/jira_ticket_helper.py (if configured) or generate the command:

# Example for a hypothetical JIRA CLI or API call
python scripts/jira_ticket_helper.py --title "[Title]" --description "[Body]" --priority "High"