القائمة
Transform informal bug descriptions into structured, professional bug reports. Use when the user describes a bug and needs it documented or filed.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Full QA audit orchestrator. Use when the user asks to "test my app", "run a full QA audit", "test everything", or invokes /qa-audit. Discovers what kind of application this is, selects the relevant QA agents (ui-inspector, api-sentinel, security-scout, perf-guardian, data-validator, regression-watcher), runs them, and merges their reports into one master QA report.
Onboard the QA toolkit onto any project. Use on first contact with a new codebase, when the user says "set up QA", "qa init", "/qa-init", or when any QA agent finds no qa-profile.md. Studies the project deeply and writes the persistent QA profile that every other agent reads first — the toolkit's long-term memory for this project.
Wire the QA suite into CI. Use when the user wants tests running automatically on every PR or on a schedule: "add this to CI", "run tests on every push", "/qa-ci". Generates GitHub Actions workflows for the generated Playwright suite and (optionally) scheduled full audits.
Self-healing for the generated test suite. Use when previously-green Playwright tests are failing, the user says "my tests broke", "fix the tests", "/qa-heal", or after a UI refactor breaks selectors. Classifies each failure (real bug vs test drift) and repairs the drift — never papers over real bugs.
Compare two QA audit runs and report what improved, what regressed, and what persists. Use when the user asks "did it improve since last time?", "compare audits", "QA trend", or invokes /qa-trend. Requires at least two timestamped runs under qa-reports/runs/.
Audit web pages for WCAG 2.1 compliance. Use when the user asks about accessibility, a11y, WCAG, screen readers, or contrast issues.
| name | bug-report-writer |
| description | Transform informal bug descriptions into structured, professional bug reports. Use when the user describes a bug and needs it documented or filed. |
Transform informal bug descriptions into professional, actionable bug reports.
This skill takes informal bug descriptions, screenshots, logs, or verbal descriptions and produces well-structured bug reports following industry best practices. Reports are formatted for Jira, GitHub Issues, or any standard bug tracking system.
When the user describes a bug or provides evidence of an issue:
## Bug Report
**Title**: [ACTION] [COMPONENT] - [Brief Description]
**Severity**: [Blocker/Critical/Major/Minor/Trivial]
**Priority**: [P0/P1/P2/P3]
**Component**: [affected module/feature]
**Environment**: [OS, Browser, App Version, API Version]
**Reported By**: [name]
**Date**: [date]
### Description
[Clear, concise description of the issue]
### Steps to Reproduce
1. [Precise step]
2. [Precise step]
3. [Precise step]
### Expected Behavior
[What should happen]
### Actual Behavior
[What actually happens]
### Frequency
[Always / Intermittent (X out of Y attempts) / One-time]
### Impact
[Who is affected and how — users, revenue, data integrity]
### Workaround
[Temporary solution if available, or "None"]
### Evidence
- Screenshots: [attached]
- Logs: [relevant log snippets]
- Console errors: [if applicable]
- Network requests: [if applicable]
### Additional Context
- First observed: [date/version]
- Related issues: [links]
- Possible root cause: [if identified]
### Labels
[regression, ui, api, data, security, performance]
Write a bug report: The checkout button doesn't work on mobile when the cart has more than 10 items. I'm using Chrome on Android.
Here's a screenshot of the error. The page crashes after I submit the form with a file larger than 5MB.