qa-skills 3.0.0 → 3.1.0

package/skills/qa-github-issues-enhanced/SKILL.md

@@ -1,175 +0,0 @@
----
-name: qa-github-issues-enhanced
-description: Enhanced GitHub Issues workflows with auto-labels, issue templates, milestone management, and structured QA workflows via GitHub MCP.
-dependencies:
-  recommended:
-    - qa-bug-ticket-creator
----
-
-# QA GitHub Issues Enhanced
-
-## Purpose
-
-Provide enhanced GitHub Issues workflows for QA automation. Extends qa-bug-ticket-creator and qa-task-creator with auto-labeling, issue templates, milestone management, search/deduplication, bulk operations, and structured QA lifecycle workflows—all via GitHub MCP.
-
-## Primary Target
-
-**GitHub** via GitHub MCP. All operations (create, search, label, milestone, bulk) use GitHub MCP APIs.
-
-## Features
-
-### Auto-Labeling
-
-Automatically assign labels based on:
-
-| Signal | Labels Applied |
-| ------ | -------------- |
-| Bug report | `type/bug`, `priority/*`, `component/*` |
-| Test coverage gap | `test-coverage-gap`, `component/*`, `status/needs-triage` |
-| Flaky test | `flaky-test`, `component/*`, `status/needs-triage` |
-| Documentation update | `docs-update`, `component/*` |
-| Enhancement request | `type/enhancement`, `component/*` |
-
-See `references/label-taxonomy.md` for full taxonomy and color codes.
-
-### Issue Templates
-
-Predefined templates for consistent structure:
-
-| Template | Use Case |
-| -------- | -------- |
-| Bug report | Defects from test failures or manual findings |
-| Test coverage gap | Gaps from qa-coverage-analyzer or spec-auditor |
-| Flaky test | Intermittent failures from qa-flaky-detector |
-| Documentation update | Spec drift, outdated docs from qa-spec-auditor |
-| Enhancement request | Feature requests, improvements |
-
-See `references/issue-templates.md` for YAML definitions.
-
-### Milestone Management
-
-- **Create** milestones per sprint/release (e.g., `Sprint 24`, `v2.1.0`)
-- **Assign** issues to milestones when creating or updating
-- **Query** issues by milestone for status reports
-
-### Structured Workflows
-
-| Workflow | Pattern |
-| -------- | ------- |
-| Bug lifecycle | bug-report → linked-PR → verification-test |
-| Coverage gap | gap → task → PR → coverage-verified |
-| Flaky test | flaky → investigation → fix → re-run |
-
-See `references/workflow-patterns.md` for detailed patterns.
-
-### Search and Deduplication
-
-Before creating new issues:
-
-1. **Search** by title keywords, component, error message, labels
-2. **Compare** similarity (same failure, component, root cause)
-3. **Link or create** — Link to duplicate or create new when no match
-
-### Bulk Operations
-
-Batch-create issues from:
-
-- **qa-coverage-analyzer** — One issue per coverage gap
-- **qa-spec-auditor** — One issue per spec drift finding
-- **qa-flaky-detector** — One issue per flaky test
-- **qa-changelog-analyzer** — One issue per recommended test
-
-## Label Taxonomy
-
-| Prefix | Purpose | Examples |
-| ------ | ------- | -------- |
-| `type/` | Issue type | `bug`, `enhancement`, `task` |
-| `priority/` | Urgency | `critical`, `high`, `medium`, `low` |
-| `component/` | Affected area | `frontend`, `backend`, `api`, `auth` |
-| `status/` | Workflow state | `needs-triage`, `in-progress`, `ready-for-test`, `verified` |
-| (no prefix) | Special QA | `test-coverage-gap`, `flaky-test`, `docs-update` |
-
-Full taxonomy in `references/label-taxonomy.md`.
-
-## Integrations
-
-| Integration | Use |
-| ----------- | --- |
-| **GitHub MCP** | All create, search, label, milestone, bulk operations |
-| **qa-bug-ticket-creator** | Consume bug reports; apply enhanced labels/templates |
-| **qa-task-creator** | Create linked tasks; apply workflow labels |
-| **qa-coverage-analyzer** | Bulk-create coverage gap issues |
-| **qa-spec-auditor** | Bulk-create spec drift issues |
-| **qa-flaky-detector** | Bulk-create flaky test issues |
-
-## Trigger Phrases
-
-- "Create GitHub issues with auto-labels for [bugs / coverage gaps / flaky tests]"
-- "Apply issue template for [bug / coverage gap / flaky test / docs / enhancement]"
-- "Create milestone for Sprint 24 / v2.1.0"
-- "Assign issues to milestone [name]"
-- "Search for similar issues before creating"
-- "Bulk-create issues from coverage analyzer output"
-- "Bulk-create issues from spec-auditor findings"
-- "Set up structured workflow for bug #123"
-
-## Workflow
-
-1. **Input** — Bug report, coverage gap, flaky test, spec finding, or bulk CSV/JSON
-2. **Template** — Select issue template (bug, coverage-gap, flaky, docs, enhancement)
-3. **Labels** — Auto-assign per taxonomy (type, priority, component, status)
-4. **Deduplication** — Search for similar open issues; link or create
-5. **Milestone** — Assign to sprint/release when provided
-6. **Create** — Create GitHub Issue via GitHub MCP
-7. **Optional** — Create linked task, PR reference, or verification issue
-
-## Scope
-
-**Can do (autonomous):**
-- Create issues with auto-labels per taxonomy
-- Apply issue templates (bug, coverage-gap, flaky, docs, enhancement)
-- Create and assign milestones
-- Search for similar issues before creating
-- Bulk-create issues from coverage/spec/flaky output
-- Link issues (bug → task, task → PR)
-- Update labels and milestone on existing issues
-
-**Cannot do (requires confirmation):**
-- Create issues in repos without write access
-- Override user-specified labels or priority
-- Assign assignees without configured mapping
-- Create milestones without user approval
-
-**Will not do (out of scope):**
-- Modify production or test code
-- Close or merge issues (stakeholder responsibility)
-- Create issues in Jira/Linear/Azure DevOps (use references for adapters)
-
-## Quality Checklist
-
-- [ ] Labels follow taxonomy (type/, priority/, component/, status/)
-- [ ] Issue template applied when creating
-- [ ] Deduplication search performed before creating
-- [ ] Milestone assigned when user provides sprint/release
-- [ ] Bulk operations include source reference (file, analyzer output)
-- [ ] No hardcoded secrets; repo/org from user input or env
-- [ ] Linked issues reference each other correctly
-
-## Troubleshooting
-
-| Symptom | Likely Cause | Fix |
-| ------- | ------------ | --- |
-| GitHub MCP create fails | Token missing, no repo access | Check `GITHUB_PERSONAL_ACCESS_TOKEN`; verify repo permissions |
-| Labels not applied | Label doesn't exist in repo | Create labels via GitHub MCP or repo settings; see label-taxonomy |
-| Duplicate not detected | Search query too narrow | Broaden keywords; search by component + error snippet |
-| Milestone not found | Milestone not created | Create milestone first; verify exact name |
-| Bulk create partial fail | Rate limit or invalid data | Check GitHub API rate limits; validate input format |
-| Wrong template applied | Misclassification of input | Ask user to confirm template; use explicit template param |
-
-## Reference Files
-
-| Topic | File |
-| ----- | ---- |
-| Label taxonomy with colors | `references/label-taxonomy.md` |
-| Issue template YAML | `references/issue-templates.md` |
-| Workflow patterns | `references/workflow-patterns.md` |

package/skills/qa-github-issues-enhanced/references/issue-templates.md

@@ -1,425 +0,0 @@
-# Issue Templates for QA GitHub Issues
-
-*YAML-based issue templates for Bug report, Test coverage gap, Flaky test, Documentation update, and Enhancement request.*
-
----
-
-## Template Location
-
-Place templates in `.github/ISSUE_TEMPLATE/` as `.yml` or `.yaml` files. GitHub will present them in the "New issue" dropdown.
-
----
-
-## 1. Bug Report
-
-**File**: `.github/ISSUE_TEMPLATE/bug_report.yml`
-
-```yaml
-name: Bug Report
-description: Report a defect or incorrect behavior
-title: "[Bug]: "
-labels: ["type/bug", "status/needs-triage"]
-assignees: []
-
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ## Bug Report
-        Provide a clear description of the defect.
-
-  - type: input
-    id: summary
-    attributes:
-      label: Summary
-      description: One-line summary of the bug
-      placeholder: "e.g., Login fails when password contains special characters"
-    validations:
-      required: true
-
-  - type: textarea
-    id: steps
-    attributes:
-      label: Steps to Reproduce
-      description: Numbered steps to reproduce
-      placeholder: |
-        1. Go to login page
-        2. Enter email and password with special chars
-        3. Click Login
-    validations:
-      required: true
-
-  - type: textarea
-    id: expected
-    attributes:
-      label: Expected Result
-      description: What should happen per spec
-      placeholder: User should be logged in successfully
-    validations:
-      required: true
-
-  - type: textarea
-    id: actual
-    attributes:
-      label: Actual Result
-      description: What actually happens
-      placeholder: Error message "Invalid credentials" appears
-    validations:
-      required: true
-
-  - type: input
-    id: environment
-    attributes:
-      label: Environment
-      description: OS, browser, app version
-      placeholder: "Windows 11, Chrome 120, app v2.1.0"
-    validations:
-      required: false
-
-  - type: dropdown
-    id: severity
-    attributes:
-      label: Severity
-      description: Impact of the defect
-      options:
-        - Blocker
-        - Critical
-        - Major
-        - Minor
-        - Trivial
-    validations:
-      required: true
-
-  - type: dropdown
-    id: component
-    attributes:
-      label: Component
-      description: Affected area
-      options:
-        - frontend
-        - backend
-        - api
-        - auth
-        - database
-        - mobile
-        - other
-    validations:
-      required: true
-
-  - type: textarea
-    id: evidence
-    attributes:
-      label: Evidence (optional)
-      description: Screenshots, logs, stack traces
-      render: shell
-    validations:
-      required: false
-```
-
----
-
-## 2. Test Coverage Gap
-
-**File**: `.github/ISSUE_TEMPLATE/test_coverage_gap.yml`
-
-```yaml
-name: Test Coverage Gap
-description: Report missing or insufficient test coverage
-title: "[Coverage]: "
-labels: ["type/test-coverage-gap", "status/needs-triage"]
-assignees: []
-
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ## Test Coverage Gap
-        Identify uncovered or under-tested code.
-
-  - type: input
-    id: summary
-    attributes:
-      label: Summary
-      description: What is not covered
-      placeholder: "e.g., AuthService.login() has 0% coverage"
-    validations:
-      required: true
-
-  - type: input
-    id: location
-    attributes:
-      label: Location
-      description: File and line or module
-      placeholder: "src/auth/AuthService.ts:42-58"
-    validations:
-      required: true
-
-  - type: dropdown
-    id: coverage_type
-    attributes:
-      label: Coverage Type
-      description: Dimension of coverage
-      options:
-        - code
-        - requirement
-        - technique
-    validations:
-      required: true
-
-  - type: textarea
-    id: rationale
-    attributes:
-      label: Rationale
-      description: Why this gap matters (risk, complexity)
-      placeholder: "High-risk payment flow; no integration tests"
-    validations:
-      required: true
-
-  - type: dropdown
-    id: component
-    attributes:
-      label: Component
-      options:
-        - frontend
-        - backend
-        - api
-        - auth
-        - database
-        - e2e
-        - unit
-        - other
-    validations:
-      required: true
-
-  - type: textarea
-    id: suggested_tests
-    attributes:
-      label: Suggested Tests (optional)
-      description: Test scenarios or techniques to add
-      render: shell
-    validations:
-      required: false
-```
-
----
-
-## 3. Flaky Test
-
-**File**: `.github/ISSUE_TEMPLATE/flaky_test.yml`
-
-```yaml
-name: Flaky Test
-description: Report an intermittent or unreliable test
-title: "[Flaky]: "
-labels: ["type/flaky-test", "status/needs-triage"]
-assignees: []
-
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ## Flaky Test Report
-        Document a test that fails intermittently.
-
-  - type: input
-    id: test_name
-    attributes:
-      label: Test Name / Path
-      description: Full test identifier
-      placeholder: "tests/e2e/login.spec.ts:42 - should login with valid credentials"
-    validations:
-      required: true
-
-  - type: dropdown
-    id: flaky_pattern
-    attributes:
-      label: Suspected Pattern
-      description: Common flaky test patterns
-      options:
-        - race-condition
-        - shared-state
-        - time-dependency
-        - external-dependency
-        - unknown
-    validations:
-      required: true
-
-  - type: input
-    id: failure_rate
-    attributes:
-      label: Failure Rate (optional)
-      description: Approximate % of runs that fail
-      placeholder: "~30%"
-    validations:
-      required: false
-
-  - type: textarea
-    id: error_message
-    attributes:
-      label: Error Message
-      description: Typical failure output
-      render: shell
-    validations:
-      required: true
-
-  - type: textarea
-    id: context
-    attributes:
-      label: Additional Context
-      description: CI logs, environment, recent changes
-    validations:
-      required: false
-```
-
----
-
-## 4. Documentation Update
-
-**File**: `.github/ISSUE_TEMPLATE/documentation_update.yml`
-
-```yaml
-name: Documentation Update
-description: Request or report documentation changes
-title: "[Docs]: "
-labels: ["type/documentation", "status/needs-triage"]
-assignees: []
-
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ## Documentation Update
-        Specify what documentation needs to be added or updated.
-
-  - type: input
-    id: summary
-    attributes:
-      label: Summary
-      description: What docs need updating
-      placeholder: "e.g., API spec section 4.2 is outdated"
-    validations:
-      required: true
-
-  - type: dropdown
-    id: doc_type
-    attributes:
-      label: Document Type
-      options:
-        - requirements
-        - specification
-        - api-contract
-        - test-plan
-        - readme
-        - runbook
-        - other
-    validations:
-      required: true
-
-  - type: textarea
-    id: description
-    attributes:
-      label: Description
-      description: What is wrong or missing
-      placeholder: "Describe the gap or inaccuracy"
-    validations:
-      required: true
-
-  - type: input
-    id: source
-    attributes:
-      label: Source (optional)
-      description: Link to spec, Figma, or requirement
-      placeholder: "URL or file path"
-    validations:
-      required: false
-```
-
----
-
-## 5. Enhancement Request
-
-**File**: `.github/ISSUE_TEMPLATE/enhancement_request.yml`
-
-```yaml
-name: Enhancement Request
-description: Propose a new feature or improvement
-title: "[Enhancement]: "
-labels: ["type/enhancement", "status/needs-triage"]
-assignees: []
-
-body:
-  - type: markdown
-    attributes:
-      value: |
-        ## Enhancement Request
-        Describe the proposed improvement.
-
-  - type: input
-    id: summary
-    attributes:
-      label: Summary
-      description: One-line description
-      placeholder: "e.g., Add retry logic for flaky API calls"
-    validations:
-      required: true
-
-  - type: textarea
-    id: problem
-    attributes:
-      label: Problem / Motivation
-      description: What problem does this solve?
-    validations:
-      required: true
-
-  - type: textarea
-    id: solution
-    attributes:
-      label: Proposed Solution
-      description: How should it work?
-    validations:
-      required: true
-
-  - type: dropdown
-    id: component
-    attributes:
-      label: Component
-      options:
-        - frontend
-        - backend
-        - api
-        - auth
-        - tests
-        - docs
-        - other
-    validations:
-      required: true
-
-  - type: textarea
-    id: alternatives
-    attributes:
-      label: Alternatives Considered (optional)
-    validations:
-      required: false
-```
-
----
-
-## Config File (Optional)
-
-**File**: `.github/ISSUE_TEMPLATE/config.yml`
-
-Use to customize the issue template chooser:
-
-```yaml
-blank_issues_enabled: true
-contact_links:
-  - name: QA Skills Documentation
-    url: https://github.com/your-org/qa-skills
-    about: Learn about QA automation skills
-```
-
----
-
-## Usage with GitHub MCP
-
-When creating issues via GitHub MCP, populate the body to match the template structure. Use the template's field IDs as keys when constructing the issue body programmatically.