Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

log-to-bug-report-converter

Étoiles2

Forks0

Mis à jour30 mars 2026 à 03:17

Parses error logs, stack traces, and test failures into production-ready bug reports.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

ShreyasBh02

ShreyasBh02/AI-Skills-Collection

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	log-to-bug-report-converter
description	Parses error logs, stack traces, and test failures into production-ready bug reports.

Log-to-Bug-Report Converter (RCA Tool)

Turn noisy log dumps into clean, actionable, developer-ready bug reports in Markdown.

Instructions

Ingest unstructured logs, stack traces, Jenkins/GitHub Actions failure outputs, or console dumps.
Analyze the root cause by finding the earliest critical exception or logical error.
Generate a structured Bug Report containing:
- Title: Clear, concise summary of the issue.
- Environment/Context: Assumptions based on stack trace (e.g., Java version, Spring Boot, OS).
- Steps to Reproduce: Derived logically from the trace/context.
- Expected Behavior: What should have happened.
- Actual Behavior: The exact failure/exception snippet.
- Root Cause Analysis (RCA): A developer-centric explanation of exactly what line/module failed and why (e.g., NullPointerException at BaseTest.java:45 due to an uninitialized WebDriver).
Use standard Markdown format so it can be easily copied to Jira, Azure DevOps, or GitHub Issues.

Plus depuis ce dépôt

même dépôt

bug-report-writer

ShreyasBh02/AI-Skills-Collection

Converts rough notes, casual descriptions, console errors, or quick observations into professional, complete bug reports — exported as a formatted Excel (.xlsx) file ready for Excel, Google Sheets, Jira, or Azure DevOps. Use this skill whenever the user mentions: "write a bug report", "log a bug", "report this issue", "found a defect", "something is broken", "create a bug ticket", "fill bug report", "document this bug", "file a ticket", "issue log", "defect report", "bug tracker", "something's wrong with", or pastes rough notes, console errors, or stack traces about unexpected behavior. Always trigger even for vague inputs like "the button doesn't work" or "this is broken" — the skill will infer details via smart assumptions and produce a professional output regardless. Trigger for single bugs AND multiple bugs described in one message.

2026-04-182

a11y-security-generator

ShreyasBh02/AI-Skills-Collection

Generates Selenium Java wrappers for axe-core accessibility testing and OWASP UI/API security checks.

2026-03-302

api-test-script-builder

ShreyasBh02/AI-Skills-Collection

Generates complete, ready-to-run API test scripts from any input — endpoint descriptions, Swagger/OpenAPI specs, Postman collections, curl commands, or plain English. Outputs working test code in the user's preferred framework: Python pytest + requests, Postman Collection (JSON), or JavaScript Jest + axios. Always trigger this skill for ANY of these situations: "API testing", "test this endpoint", "write API tests", "generate test cases", "Postman collection", "pytest for API", "REST API test", "API automation", "validate API response", "check my endpoint", "test my routes", "QA this API", sharing a Swagger/OpenAPI spec, sharing a curl command, sharing an API route or payload, or any request involving HTTP endpoint verification. Trigger even for vague inputs like "test this" when an API context is present — structured, runnable scripts are always better than ad-hoc manual testing.

2026-03-302

daily-planner-prioritizer

ShreyasBh02/AI-Skills-Collection

Creates a smart, time-blocked daily plan from a user's task dump, meetings, errands, habits, and goals — then outputs BOTH a clean text summary in chat AND a formatted Excel (.xlsx) schedule file. Covers work tasks, meetings, personal errands, health/exercise reminders, and QA-specific tasks (test runs, bug triage, reviews). Use this skill whenever the user mentions: "plan my day", "prioritize my tasks", "make a schedule", "I have too much to do", "help me organize today", "daily planner", "time block my day", "what should I do first", "morning routine", "task list for today", or dumps a list of things to do. Always trigger even for partial inputs — a rough list of tasks is enough to generate a useful plan. The more context given, the better, but never require it.

2026-03-302

email-message-rewriter

ShreyasBh02/AI-Skills-Collection

Rewrites, polishes, or drafts emails and messages from rough notes, bullet points, or poorly worded drafts — in the right tone for the situation. Handles professional emails, Slack messages, WhatsApp texts, follow-ups, apologies, feedback, and more. Use this skill whenever the user says: "rewrite this email", "make this sound professional", "write an email for me", "help me reply to this", "make this polite", "draft a message", "how do I say this nicely", "write a follow-up", "make this less aggressive", "I need to send this but don't know how to word it", or shares a rough draft asking for improvements. Always trigger — even for short messages. A one-line rewrite is still worth doing well.

2026-03-302

flaky-test-healer

ShreyasBh02/AI-Skills-Collection

Analyzes and refactors flaky UI tests written in Selenium WebDriver with Java.

2026-03-302

name	log-to-bug-report-converter
description	Parses error logs, stack traces, and test failures into production-ready bug reports.

Log-to-Bug-Report Converter (RCA Tool)

Turn noisy log dumps into clean, actionable, developer-ready bug reports in Markdown.

Instructions

Ingest unstructured logs, stack traces, Jenkins/GitHub Actions failure outputs, or console dumps.
Analyze the root cause by finding the earliest critical exception or logical error.
Generate a structured Bug Report containing:
- Title: Clear, concise summary of the issue.
- Environment/Context: Assumptions based on stack trace (e.g., Java version, Spring Boot, OS).
- Steps to Reproduce: Derived logically from the trace/context.
- Expected Behavior: What should have happened.
- Actual Behavior: The exact failure/exception snippet.
- Root Cause Analysis (RCA): A developer-centric explanation of exactly what line/module failed and why (e.g., NullPointerException at BaseTest.java:45 due to an uninitialized WebDriver).
Use standard Markdown format so it can be easily copied to Jira, Azure DevOps, or GitHub Issues.