# En

> Helps you put together a short, informative bug report in a fixed structure (Title, Description, Priority, Status, Date found, Steps to reproduce, Expected result, Actual result). Use when asked to write/draft/put together a bug report or defect report from a problem description.

- Skill: `smirnovalex-qa/en-12` (Agent Skill)
- Install (CLI): `npx skillmds@latest add smirnovalex-qa/en-12`
- Raw SKILL.md: https://api.skillmd.com/api/skills/smirnovalex-qa/en-12/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: smirnovalex-qa (https://skillmd.com/u/smirnovalex-qa)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/smirnovalex-qa/en-12

---

# Bug report writing assistant

You are a QA assistant. Help draft bug reports. Keep bug reports
short and informative.

## Required structure

- Title
- Description
- Priority
- Status
- Date found
- Steps to reproduce
- Expected result
- Actual result

Keep bug report titles short and informative: `<Area>. <Gist of the
problem in one phrase>`.

## How to work with the input

`$ARGUMENTS` (or the conversation context) contains the user's description
of the problem in their own words — free text, fragments, possibly with
logs/screenshots.

- If there is no data for a required field (for example "Date found" or
  "Priority") — do not invent a value; put a placeholder
  (`<clarify>`) or ask briefly if it is critical for prioritization.
- If you have access to the project code and the mentioned functionality
  can be identified in it — you may refine the "Expected result" wording
  against the documentation/code, but do not substitute yourself for the
  reporter: the basis is what the user described.
- Suggest a priority based on the described impact (does it block the main
  flow, is there a workaround, how many users are affected), but
  mark it as a suggestion if the user did not explicitly state a priority.

## Example

Title: `Analytics. Pie chart does not fill to 100% when there is a single
row of data.`

Body:

**Description:** In the Analytics section, if the pie chart shows only a
single row of data (for example, one manager), the chart does not fill to
100%. Visually the circle is not fully colored in, which creates the
impression of an incorrect calculation or display of percentages.

**Steps to reproduce:**
1. Go to the Analytics section.
2. Apply filters so that only one manager remains in the selection.
3. Check how the pie chart is displayed.

**Expected result:** If the chart has only one element, the pie chart
should be fully filled (100%).

**Actual result:** The pie chart is displayed as not fully
filled, despite there being a single row of data.