qa-defect

النجوم٢

التفرعات١

آخر تحديث٢٢ يوليو ٢٠٢٦ في ١٣:١٥

[QA Method] Defect management lifecycle: JIRA Bug Workflow, triage, classification, report validation, verification protocol, defect metrics.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

المصدر

VirtoCommerce

VirtoCommerce/vc-mcp-testing-module

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

محللو ضمان جودة البرمجيات والمختبرونمهن الحاسوب والرياضيات·SOC 15-1253

مستكشف الملفات

3 ملفات

SKILL.md

readonly

name	qa-defect
description	[QA Method] Defect management lifecycle: JIRA Bug Workflow, triage, classification, report validation, verification protocol, defect metrics.
argument-hint	triage VCST-XXXX \| verify VCST-XXXX \| classify \| workflow \| metrics
disable-model-invocation	true

/qa-defect — Defect Management Lifecycle

Manages the full defect lifecycle from detection through triage, classification, fix verification, and closure. Provides the JIRA Bug Workflow (16 statuses), triage routing, report validation, verification protocol, and defect process health metrics.

Usage

/qa-defect                       # Full lifecycle overview + JIRA workflow map
/qa-defect triage VCST-1234      # Triage a bug: validate report, check duplicates, classify, assign
/qa-defect verify VCST-1234      # Verify a fix: re-run STR, check regression, transition JIRA
/qa-defect classify              # Show defect type taxonomy + root cause categories
/qa-defect workflow              # Show JIRA Bug Workflow (16 statuses, all transitions)
/qa-defect metrics               # Defect process health: aging, MTTR, reopen rate, escape rate

Execution

Load defect-lifecycle-workflow.md from this skill folder.
Determine context from argument:
- No argument → full lifecycle overview with JIRA workflow diagram
- triage VCST-XXXX → triage workflow
- verify VCST-XXXX → fix verification protocol
- classify → defect type taxonomy + root cause categories
- workflow → JIRA Bug Workflow diagram + transition table
- metrics → defect process health indicators
For triage: Resolve ticket via tracker-ops (Jira MCP getJiraIssue / ado.mjs get-workitem, per profile) → validate report completeness (12-item checklist) → check for duplicates (tracker-ops §2 Search — Jira JQL summary ~ "keyword" AND status != Cancelled, Azure WIQL equivalent) → classify defect type + root cause → assess severity + priority (reference /qa-risk) → route to owner via triage matrix → set fields + recommend the destination role (§0 role table), transitioned via tracker-ops.
For verify: Resolve ticket + linked PR via tracker-ops → confirm fix is deployed → execute original STR verbatim (must pass 3 consecutive times) → run 2-3 adjacent regression checks → check for side effects (console errors, network failures) → decision: all pass → transition role tested then done; any fail → transition role reopen with new evidence. All transitions resolve the live workflow via tracker-ops (§0 roles), honoring tracker.azure.transitionPolicy.
For classify: Show defect type taxonomy (8 types) and root cause categories (6 categories) from defect-lifecycle-workflow.md section 6. Suggest classification for the given bug based on symptoms.
For workflow: Show the §0 role→transition table first (the tracker-agnostic layer), then the JIRA Bug Workflow ASCII diagram and full transition table from defect-lifecycle-workflow.md sections 1-3 as the Jira reference example. Highlight QA-owned transitions.
For metrics: Compute defect process health indicators from JIRA data using JQL queries. Report aging, MTTR, reopen rate, escape rate, density, and verification pass rate against targets.
For bug report templates, load defect-report-templates.md from this skill folder (frontend + backend templates).

Integration with Other Skills

Direction	Skill	Relationship
Upstream	`/qa-investigate`	Bug investigation produces the defect that enters this lifecycle
Upstream	`/qa-evidence`	Evidence capture standards used in report validation
Upstream	`/qa-risk`	Severity/Priority classification (independent dimensions)
Upstream	`/qa-bug` (command)	Bug filing creates the ticket this skill manages
Downstream	`/qa-fix` (command)	A ready, routable ticket is picked up for autonomous fix

Rules

Never transition a bug (any tracker) without documenting the reason in a comment; transition by §0 role via tracker-ops, never by a hardcoded transition name.
Always validate report completeness before triaging — missing STR = send back to reporter.
Verification must re-run original STR (3x) + check at least 1 adjacent flow for regression.
Duplicate check is mandatory before filing any new bug.
Severity and Priority are independent dimensions — always set both explicitly.
Escalate P0 bugs not picked up within 2 hours, P1 bugs not assigned within 1 business day.

المزيد من هذا المستودع

نفس المستودع

project-init

VirtoCommerce/vc-mcp-testing-module

Initialize / onboard this agentic-QA plugin onto a deployment. Installs deps, then asks the operator only what genuinely shapes the config — the environment NAME, the bug tracker (Jira / Azure Boards), the code host (GitHub / Azure Repos), and an auth preference per axis (PAT recommended, else browser/CLI login). Everything else — whether it is a native-platform or a CLIENT project, the client org, the contribution mode, the fork account — is DERIVED from the token + the filled env + a live module/repo scan. Writes project-profile.json + .env.<env> + .env.local + .mcp.json and verifies access. The whole point is to make /qa-fix route each bug to the RIGHT repo (client custom code vs native platform) and file to the RIGHT tracker. Use when standing the plugin up on a new machine or for a new customer.

2026-07-232

project-init

VirtoCommerce/vc-mcp-testing-module

2026-07-232

qa-deploy-pr

VirtoCommerce/vc-mcp-testing-module

[QA Methodology] Gather ALL fresh CI prerelease artifacts for a change (modules + platform + vc-frontend) and deploy them together to the test env (vc-deploy-dev@<TEST_ENV branch>) in ONE manifest update: resolve a tracker ticket's linked PRs across all repos (or an explicit --module/--platform/--theme/--pr set) → each PR's latest vc3prerelease build → minimal-diff repin of backend/packages.json (AzureBlob/BlobName + PlatformVersion) and theme/artifact.json → dry-run combined diff (default) or a gated deploy PR (direct same-repo when the account has write, else a fork PR) → --verify polls the env-branch pin + /api/platform/modules per target. Never merges (a human merges to deploy); writes route through gh's keyring token; prints the web-edit URL when it can't push. Unblocks /qa-test PR#N and /qa-verify-fix.

2026-07-232

qa-review-bl

VirtoCommerce/vc-mcp-testing-module

[QA Method] Triangulate each BL invariant against docs + live + source code, auto-apply confirmed changes to business-logic.md, and reconcile test-case coverage. Delegates the live axis to qa-testing-expert; runs the triangulation via ba-system-analyzer.

2026-07-222

qa-local-env

VirtoCommerce/vc-mcp-testing-module

Bring up a local Virto Commerce stack (backend + storefront + DB + ES) via start-local, pinned to the ACTUAL deployed package manifest (vc-deploy-dev @ vcptcore-demo); optionally augment it with the module/PR versions a JIRA task needs. Use when asked to spin up / run / provision a local VC environment, reproduce a deployed env locally, or stand up an env to test a specific ticket.

2026-07-222

qa-defect

VirtoCommerce/vc-mcp-testing-module

[QA Method] Defect management lifecycle: JIRA Bug Workflow, triage, classification, report validation, verification protocol, defect metrics.

2026-07-222

/qa-defect — Defect Management Lifecycle

Usage

/qa-defect # Full lifecycle overview + JIRA workflow map /qa-defect triage VCST-1234 # Triage a bug: validate report, check duplicates, classify, assign /qa-defect verify VCST-1234 # Verify a fix: re-run STR, check regression, transition JIRA /qa-defect classify # Show defect type taxonomy + root cause categories /qa-defect workflow # Show JIRA Bug Workflow (16 statuses, all transitions) /qa-defect metrics # Defect process health: aging, MTTR, reopen rate, escape rate

Execution

Load defect-lifecycle-workflow.md from this skill folder.

Determine context from argument:

No argument → full lifecycle overview with JIRA workflow diagram
triage VCST-XXXX → triage workflow
verify VCST-XXXX → fix verification protocol
classify → defect type taxonomy + root cause categories
workflow → JIRA Bug Workflow diagram + transition table
metrics → defect process health indicators

For triage: Resolve ticket via tracker-ops (Jira MCP getJiraIssue / ado.mjs get-workitem, per profile) → validate report completeness (12-item checklist) → check for duplicates (tracker-ops §2 Search — Jira JQL summary ~ "keyword" AND status != Cancelled, Azure WIQL equivalent) → classify defect type + root cause → assess severity + priority (reference /qa-risk) → route to owner via triage matrix → set fields + recommend the destination role (§0 role table), transitioned via tracker-ops.

For verify: Resolve ticket + linked PR via tracker-ops → confirm fix is deployed → execute original STR verbatim (must pass 3 consecutive times) → run 2-3 adjacent regression checks → check for side effects (console errors, network failures) → decision: all pass → transition role tested then done; any fail → transition role reopen with new evidence. All transitions resolve the live workflow via tracker-ops (§0 roles), honoring tracker.azure.transitionPolicy.

For classify: Show defect type taxonomy (8 types) and root cause categories (6 categories) from defect-lifecycle-workflow.md section 6. Suggest classification for the given bug based on symptoms.

For workflow: Show the §0 role→transition table first (the tracker-agnostic layer), then the JIRA Bug Workflow ASCII diagram and full transition table from defect-lifecycle-workflow.md sections 1-3 as the Jira reference example. Highlight QA-owned transitions.

For metrics: Compute defect process health indicators from JIRA data using JQL queries. Report aging, MTTR, reopen rate, escape rate, density, and verification pass rate against targets.

For bug report templates, load defect-report-templates.md from this skill folder (frontend + backend templates).

Integration with Other Skills

Direction

Skill

Relationship

Upstream

/qa-investigate

Bug investigation produces the defect that enters this lifecycle

Upstream

/qa-evidence

Evidence capture standards used in report validation

Upstream

/qa-risk

Severity/Priority classification (independent dimensions)

Upstream

/qa-bug (command)

Bug filing creates the ticket this skill manages

Downstream

/qa-fix (command)

A ready, routable ticket is picked up for autonomous fix

Rules

Never transition a bug (any tracker) without documenting the reason in a comment; transition by §0 role via tracker-ops, never by a hardcoded transition name.

Always validate report completeness before triaging — missing STR = send back to reporter.

Verification must re-run original STR (3x) + check at least 1 adjacent flow for regression.

Duplicate check is mandatory before filing any new bug.

Severity and Priority are independent dimensions — always set both explicitly.

Escalate P0 bugs not picked up within 2 hours, P1 bugs not assigned within 1 business day.