القائمة
Quick bug report in Jira. Invoke via /bug-report. Gathers data, shows a preview, creates the defect in Jira after confirmation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Составление тест-кейсов по best practice QA с экспортом в CSV для импорта в Zephyr Scale (Option 1) или созданием напрямую через MCP вашей TMS. Используй, когда пользователь просит сгенерировать, составить или подготовить тест-кейсы, чек-листы или CSV для импорта в TMS.
Test case authoring per QA best practices, with CSV export for Zephyr Scale import (Option 1) or direct creation via your TMS MCP. Use when the user asks to generate, write, or prepare test cases, checklists, or CSV for TMS import.
Универсальный фреймворк тестирования (frontend + backend) — дотошный прогон любой задачи на тестирование с доказательной дисциплиной. Используй, когда нужно протестировать фичу/форму/билд/API/сервис, составить план тестирования, прогнать проверки, провести исследовательское или регрессионное тестирование, найти дефекты.
Universal testing framework (frontend + backend) — a meticulous run of any testing task with evidence discipline. Use when you need to test a feature/form/build/API/service, draft a test plan, run checks, perform exploratory or regression testing, or find defects.
Ревью только что написанных или изменённых автотестов на соответствие best practices TypeScript + Playwright (по официальной документации) и конвенциям вашего проекта. Используй по /test-review либо после написания/правки любого теста (UI E2E, API, UI+API, моки, visual, mobile) или Page Object/фикстуры/констант — до коммита. Выдаёт приоритизированный список замечаний с severity, привязкой к строкам и готовыми фиксами.
Review of just-written or modified autotests against TypeScript + Playwright best practices (per official documentation) and your project's conventions. Use via /test-review or after writing/editing any test (UI E2E, API, UI+API, mocks, visual, mobile) or a Page Object/fixture/constants — before commit. Produces a prioritized list of findings with severity, line references, and ready-made fixes.
| name | bug-report |
| description | Quick bug report in Jira. Invoke via /bug-report. Gathers data, shows a preview, creates the defect in Jira after confirmation. |
| disable-model-invocation | true |
| allowed-tools | ["AskUserQuestion","mcp__atlassian__jira_create_issue","mcp__atlassian__jira_update_issue","mcp__atlassian__jira_search_fields","mcp__atlassian__jira_get_field_options","mcp__atlassian__jira_get_issue"] |
You help file a bug in Jira quickly. Follow this algorithm:
The values below are an example; adapt them to your instance (right here or in the project's CLAUDE.md):
PROJBug (check the exact type name in your project - in localized instances the type may be named differently, e.g. "Defect"/«Дефект» in Russian ones)customfield_XXXXX (Team): "..."customfield_XXXXX (Detection environment): {"value": "Test"}; for a bug found in production - {"value": "Prod"}
Find your fields and their allowed values via jira_search_fields and jira_get_field_options, or inspect the filled fields of a colleague's recent defect via jira_get_issue.If the user passed the bug description in the arguments - use it. If not - ask questions via AskUserQuestion:
Required data:
Optional:
Type and priority - per the configuration (section 0).
Summary: a brief description of the problem, no [BUG] prefixes or similar.
Description structure - plain text with bold headers:
**Steps to reproduce:**
1. Step 1
2. Step 2
**Actual result:**
Description of what happens.
**Expected result:**
Description of what should happen.
**Environment:**
Environment/browser/device.
If preconditions are needed - add a Preconditions: block before the steps. If there is useful context - add an Additional info: block at the end.
ALWAYS show the user the full ticket text and wait for confirmation before calling mcp__atlassian__jira_create_issue. Preview format:
**Type:** Bug
**Priority:** Medium
**Assignee:** (if specified)
**Project:** PROJ
**Summary:** ...
**Description:**
(full description text)
Only after explicit confirmation ("yes", "ok", "create it") - call the creation API.
Output the key and link of the created ticket. If the assignee was not set - warn the user.
Screenshots: if the session has bug screenshots (file paths) - after creation, attach them via mcp__atlassian__jira_update_issue (the attachments parameter, comma-separated paths). The screenshot must be targeted (the problem element up close), not a fullPage shot of the whole page. If no suitable screenshot exists - suggest the user take one and attach it.