Thitic9203

helix

Helix QA assistant menu — route to TC FE prep, TC API prep, retest bug, testing ticket, or create bug. Use when the user says Helix, /helix, QA assistant menu, or is unsure which QA workflow to run. Do NOT use when the user already chose a specific workflow — use the matching command (/tc-fe-prep, /tc-api-prep, /retest-bug, /testing-ticket, /create-bug) directly.

create-bug-workflow

Open bug reports on Jira or GitHub after collecting target link, format template, and bug details — confirm before creating. Use when the user chooses Create bug from Helix, invokes /create-bug, or wants issues filed from test findings. Do NOT use for Playwright test runs (testing-ticket-workflow), retest-after-fix (retest-bug-workflow), posting manual TC tables (tc-fe-prep / tc-api-prep), or updating test result sheets without filing bugs.

retest-bug-workflow

Retest a Jira bug after a dev fix — read ticket, test API or UI, compare Swagger, draft evidence, post comment (with approval), transition and assign back to dev. Use when the user says retest bug, verify fix, check if an issue is fixed, /retest-bug, or Retest bug from Helix. Do NOT use for writing new FE/API test case tables (tc-fe-prep / tc-api-prep), full ticket Playwright runs (testing-ticket-workflow), or opening new bugs (create-bug-workflow).

tc-api-prep-workflow

Prepare API manual test cases from API spec and Swagger with mandatory spec/Swagger coverage review and ISTQB/29119-3 quality check — confirm columns and delivery (Jira comment link and/or CSV/Excel in workspace). Use when the user chooses TC API Preparation from Helix, invokes /tc-api-prep, or asks for API test cases from Swagger/OpenAPI. Do NOT use for frontend story AC/EC tables (tc-fe-prep-workflow), Playwright or test execution (testing-ticket-workflow), retest-after-fix (retest-bug-workflow), or opening bugs (create-bug-workflow).

tc-fe-prep-workflow

Prepare frontend manual test cases from a Jira story (AC/EC) with mandatory AC/EC coverage review and ISTQB/29119-3 quality check, then draft table in chat, export CSV/Excel, publish one comment on that story only, and close with a four-axis final TC review report (AC/EC alignment, spelling, numbering, scope). Use when the user asks for FE test cases, manual TC from acceptance criteria, draft TC comment on Jira, or TC FE Preparation from Helix (/tc-fe-prep). Do NOT use for API-only Swagger test cases (tc-api-prep-workflow), Playwright execution (testing-ticket-workflow), retest-after-fix (retest-bug-workflow), or opening bug tickets (create-bug-workflow).

Testing & QA Listed

testing-ticket-workflow

Test one Jira ticket with Playwright after intake and confirmation — summarize results in chat, then optionally update an external results destination. Use for Testing ticket from Helix, /testing-ticket, or when the user wants automated UI/API checks for a single ticket. Do NOT use for opening bug tickets (create-bug-workflow), retest-after-fix on a bug (retest-bug-workflow), or drafting manual TC tables (tc-fe-prep / tc-api-prep). Does not run full-app regression.