qa-skills 3.0.0

package/skills/qa-supertest-writer/references/patterns.md

@@ -0,0 +1,242 @@
+# Supertest Patterns
+
+## CRUD Endpoints
+
+### GET (List)
+
+```ts
+describe('GET /users', () => {
+  it('returns 200 with user list', async () => {
+    const res = await request(app)
+      .get('/users')
+      .expect(200)
+      .expect('Content-Type', /json/)
+
+    expect(res.body).toHaveProperty('users')
+    expect(Array.isArray(res.body.users)).toBe(true)
+  })
+
+  it('returns 401 when unauthenticated', () =>
+    request(app).get('/users').expect(401))
+})
+```
+
+### GET (Single)
+
+```ts
+describe('GET /users/:id', () => {
+  it('returns 200 with user', async () => {
+    const res = await request(app)
+      .get('/users/1')
+      .set('Authorization', `Bearer ${token}`)
+      .expect(200)
+
+    expect(res.body).toMatchObject({ id: 1, email: expect.any(String) })
+  })
+
+  it('returns 404 when not found', () =>
+    request(app)
+      .get('/users/99999')
+      .set('Authorization', `Bearer ${token}`)
+      .expect(404))
+})
+```
+
+### POST (Create)
+
+```ts
+describe('POST /users', () => {
+  it('returns 201 with created user', async () => {
+    const res = await request(app)
+      .post('/users')
+      .set('Content-Type', 'application/json')
+      .send({ email: 'test@example.com', name: 'Test User' })
+      .expect(201)
+
+    expect(res.body).toHaveProperty('id')
+    expect(res.body.email).toBe('test@example.com')
+  })
+
+  it('returns 400 on validation error', () =>
+    request(app)
+      .post('/users')
+      .set('Content-Type', 'application/json')
+      .send({ email: 'invalid' })
+      .expect(400))
+})
+```
+
+### PUT/PATCH (Update)
+
+```ts
+describe('PUT /users/:id', () => {
+  it('returns 200 with updated user', async () => {
+    const res = await request(app)
+      .put('/users/1')
+      .set('Authorization', `Bearer ${token}`)
+      .send({ name: 'Updated Name' })
+      .expect(200)
+
+    expect(res.body.name).toBe('Updated Name')
+  })
+})
+```
+
+### DELETE
+
+```ts
+describe('DELETE /users/:id', () => {
+  it('returns 204 on success', () =>
+    request(app)
+      .delete('/users/1')
+      .set('Authorization', `Bearer ${token}`)
+      .expect(204))
+
+  it('returns 404 when not found', () =>
+    request(app)
+      .delete('/users/99999')
+      .set('Authorization', `Bearer ${token}`)
+      .expect(404))
+})
+```
+
+## Authentication
+
+### Bearer Token
+
+```ts
+let token: string
+
+beforeAll(async () => {
+  const res = await request(app)
+    .post('/auth/login')
+    .send({ email: 'test@example.com', password: 'secret' })
+  token = res.body.token
+})
+
+it('accesses protected route', () =>
+  request(app)
+    .get('/users')
+    .set('Authorization', `Bearer ${token}`)
+    .expect(200))
+```
+
+### API Key
+
+```ts
+request(app)
+  .get('/api/data')
+  .set('X-API-Key', process.env.TEST_API_KEY)
+  .expect(200)
+```
+
+### Cookies (Session)
+
+```ts
+const agent = request.agent(app)
+
+beforeAll(async () => {
+  await agent
+    .post('/auth/login')
+    .send({ email: 'test@example.com', password: 'secret' })
+    .expect(200)
+})
+
+it('uses session cookie', () => agent.get('/users').expect(200))
+```
+
+### Basic Auth
+
+```ts
+request(app)
+  .get('/admin')
+  .auth('user', 'password')
+  .expect(200)
+```
+
+## File Upload
+
+```ts
+import path from 'path'
+
+describe('POST /upload', () => {
+  it('uploads file and returns 201', async () => {
+    const res = await request(app)
+      .post('/upload')
+      .attach('file', path.join(__dirname, 'fixtures/sample.pdf'))
+      .expect(201)
+
+    expect(res.body).toHaveProperty('url')
+  })
+
+  it('returns 400 when no file', () =>
+    request(app).post('/upload').expect(400))
+})
+```
+
+## Error Responses
+
+```ts
+it('returns 400 with validation errors', async () => {
+  const res = await request(app)
+    .post('/users')
+    .send({})
+    .expect(400)
+
+  expect(res.body).toHaveProperty('errors')
+  expect(Array.isArray(res.body.errors)).toBe(true)
+})
+
+it('returns 500 structure on server error', async () => {
+  const res = await request(app)
+    .get('/trigger-error')
+    .expect(500)
+
+  expect(res.body).toMatchObject({
+    error: expect.any(String),
+    message: expect.any(String),
+  })
+})
+```
+
+## Pagination
+
+```ts
+describe('GET /users with pagination', () => {
+  it('returns paginated results', async () => {
+    const res = await request(app)
+      .get('/users?page=1&limit=10')
+      .expect(200)
+
+    expect(res.body).toMatchObject({
+      users: expect.any(Array),
+      total: expect.any(Number),
+      page: 1,
+      limit: 10,
+    })
+    expect(res.body.users.length).toBeLessThanOrEqual(10)
+  })
+
+  it('returns 400 for invalid page', () =>
+    request(app).get('/users?page=-1').expect(400))
+})
+```
+
+## Query Parameters
+
+```ts
+request(app)
+  .get('/search')
+  .query({ q: 'test', limit: 5 })
+  .expect(200)
+```
+
+## Custom Headers
+
+```ts
+request(app)
+  .get('/api/data')
+  .set('X-Request-ID', 'test-123')
+  .set('Accept', 'application/json')
+  .expect(200)
+```

package/skills/qa-task-creator/SKILL.md

@@ -0,0 +1,142 @@
+---
+name: qa-task-creator
+description: Generate work tasks from QA analysis, coverage gaps, and bug reports. Works standalone for any task creation or paired with qa-bug-ticket-creator for linked fix tasks.
+dependencies:
+  recommended:
+    - qa-bug-ticket-creator
+---
+
+# QA Task Creator
+
+## Purpose
+
+Generate structured work tasks from QA analysis outputs, coverage gaps, spec-auditor findings, risk-analyzer results, and bug reports. Supports two usage patterns: **standalone** (create tasks directly from user request) and **paired** with qa-bug-ticket-creator (auto-create linked fix/enhancement tasks from bugs).
+
+## Dual-Use Pattern
+
+| Mode | Trigger | Output |
+| ---- | ------- | ------ |
+| **Standalone** | User requests task creation from description, coverage gap, or spec finding | GitHub Issue (or Jira/Linear format) with full task details |
+| **Paired** | Bug ticket created by qa-bug-ticket-creator | Linked fix task referencing the bug; optionally enhancement tasks for related improvements |
+
+When paired: bug ticket → fix task; fix task links back to bug via GitHub issue reference (e.g., "Fixes #123").
+
+## Input Sources
+
+| Source | Task Type | Example |
+| ------ | --------- | ------- |
+| **Coverage gaps** | Development / QA | "Add unit tests for AuthService.login() — 0% coverage" |
+| **Spec-auditor findings** | Development / Documentation | "Implement validation per spec section 4.2" |
+| **Risk-analyzer output** | Development / QA | "Add integration tests for payment flow — high risk" |
+| **Bug reports** | Development (fix) | "Fix null pointer in checkout when cart is empty" |
+| **User request** | Any | "Create task to refactor user API" |
+
+## Task Types
+
+| Type | Description | Typical Assignee |
+| ---- | ----------- | ---------------- |
+| **Development** | Implement, fix, refactor, optimize | Dev |
+| **QA** | Write tests, increase coverage, update test data | QA |
+| **Documentation** | Update specs, add diagrams, API docs | Dev/QA |
+| **Enhancement** | Performance, validation, UI polish | Dev |
+
+See `references/task-types.md` for templates and examples.
+
+## Output Format
+
+Tasks follow GitHub Issue / Jira / Linear story format:
+
+- **Title** — Clear, actionable (verb + object)
+- **Description** — Context, acceptance criteria, links to source
+- **Labels** — `task`, `development`, `qa`, `documentation`, `enhancement`, component tags
+- **Links** — Parent bug, requirement, coverage gap, or spec section
+- **Acceptance criteria** — Testable conditions for done
+
+## Auto-Linking
+
+Tasks automatically link to their source:
+
+| Source | Link Format |
+| ------ | ----------- |
+| Bug | "Fixes #123" or "Related to #123" in body; GitHub auto-links |
+| Requirement | Link to requirement doc or ticket |
+| Coverage gap | File:line reference, module name |
+| Spec section | Section reference (e.g., "Spec §4.2") |
+
+See `references/linking-patterns.md` for patterns.
+
+## Integrations
+
+| Integration | Use |
+| ----------- | --- |
+| **GitHub MCP** | Create issues, search for duplicates, link to bugs |
+| **qa-bug-ticket-creator** | Consume bug ticket output; create linked fix task |
+| **qa-coverage-analyzer** | Consume coverage gap output |
+| **qa-spec-writer / qa-requirements-generator** | Consume spec/requirement references |
+
+## Trigger Phrases
+
+- "Create a task to [description]"
+- "Generate fix task for bug #123"
+- "Create tasks from coverage gaps in [path]"
+- "Task from spec-auditor findings"
+- "Linked fix task for [bug summary]"
+- "Work items from risk analysis"
+- "Development task for [feature/fix]"
+
+## Workflow
+
+1. **Input** — User request, bug ticket, coverage gap, spec finding, or risk output
+2. **Task type** — Classify as Development / QA / Documentation / Enhancement
+3. **Content** — Title, description, acceptance criteria, labels
+4. **Links** — Add references to parent bug, requirement, or source
+5. **Duplicate check** — Search existing issues for similar tasks (optional)
+6. **Create** — Create GitHub Issue via GitHub MCP; output link
+
+## Scope
+
+**Can do (autonomous):**
+- Create tasks from user description, bug tickets, coverage gaps, spec findings
+- Classify task type and assign appropriate labels
+- Link tasks to parent bugs, requirements, coverage gaps
+- Create GitHub Issues via GitHub MCP
+- Search for duplicate tasks before creating
+- Work paired with qa-bug-ticket-creator for linked fix tasks
+
+**Cannot do (requires confirmation):**
+- Assign to specific users without approval
+- Set milestones or due dates without user input
+- Create tasks in Jira/Linear (reference format only; adapters future)
+
+**Will not do (out of scope):**
+- Execute development or testing work
+- Modify code or configurations
+- Approve or prioritize tasks (stakeholder responsibility)
+
+## Quality Checklist
+
+- [ ] Task title is actionable (verb + object)
+- [ ] Description includes context and acceptance criteria
+- [ ] Links to parent bug/requirement/coverage gap when applicable
+- [ ] Labels match task type and component
+- [ ] Acceptance criteria are testable
+- [ ] No hardcoded secrets; repo/org from user or env
+- [ ] Duplicate check performed when creating from coverage/spec
+
+## Troubleshooting
+
+| Symptom | Likely Cause | Fix |
+| ------- | ------------ | --- |
+| Task too vague | Insufficient context from source | Add explicit acceptance criteria; request clarification |
+| Missing link to bug | Bug ticket not passed or not found | Verify bug exists; include bug number in description |
+| Wrong task type | Misclassification of input | Use `references/task-types.md`; ask user to confirm |
+| Duplicate created | Search query too narrow | Broaden search terms; check similar open issues |
+| GitHub MCP fails | Token missing, repo access | Verify GitHub MCP config; use markdown output as fallback |
+| Paired mode not linking | qa-bug-ticket-creator output not consumed | Ensure bug ticket number is passed; use "Fixes #N" in body |
+
+## Reference Files
+
+| Topic | File |
+| ----- | ---- |
+| Task type templates and examples | `references/task-types.md` |
+| Linking patterns (bugs, requirements, coverage) | `references/linking-patterns.md` |

package/skills/qa-task-creator/references/linking-patterns.md

@@ -0,0 +1,127 @@
+# Linking Patterns for Tasks
+
+*How to link tasks to bugs, requirements, coverage gaps, and spec sections.*
+
+---
+
+## GitHub Issue Linking
+
+### Fixes (auto-close)
+
+Use in issue body or PR description:
+```
+Fixes #123
+```
+or
+```
+Closes #123
+```
+GitHub will auto-close issue #123 when the PR is merged.
+
+### Related (no auto-close)
+
+```
+Related to #123
+```
+or
+```
+See also #456
+```
+
+### In title (avoid)
+
+Do not put issue numbers in task titles; use the body for links.
+
+---
+
+## Bug → Fix Task
+
+**Pattern:** Bug ticket created first; fix task references it.
+
+1. **qa-bug-ticket-creator** creates bug #123
+2. **qa-task-creator** creates fix task with body:
+   ```
+   Fixes #123
+   
+   [Task description and acceptance criteria]
+   ```
+3. When fix PR is merged, GitHub auto-closes #123
+
+**When to use "Fixes" vs "Related to":**
+- **Fixes** — Task directly resolves the bug
+- **Related to** — Task is related (e.g., adds test for bug; doesn't fix root cause)
+
+---
+
+## Requirement → Task
+
+**Pattern:** Task implements or validates a requirement.
+
+**Link format:**
+```
+Implements: REQ-001 (User must be able to reset password)
+```
+or
+```
+Requirement: [link to requirement doc] §2.3
+```
+
+**Traceability:** Keep requirement ID in task body for traceability matrix.
+
+---
+
+## Coverage Gap → Task
+
+**Pattern:** Coverage analyzer identifies gap; task adds tests.
+
+**Link format:**
+```
+Coverage gap: src/auth/AuthService.ts:45-78 (0% coverage)
+```
+or
+```
+Module: AuthService.login() — 0% coverage per coverage report [date]
+```
+
+**File:line** helps developer locate the code to test.
+
+---
+
+## Spec Section → Task
+
+**Pattern:** Spec-auditor or manual review finds discrepancy; task updates implementation or spec.
+
+**Link format:**
+```
+Spec reference: §4.2 Validation Rules
+```
+or
+```
+Spec: docs/spec.md §4.2 — Implement validation per spec
+```
+
+---
+
+## Chained Links (Bug → Fix → Test)
+
+When creating a fix task, consider also creating a QA task for regression coverage:
+
+1. **Bug #123** — "Checkout crashes with empty cart"
+2. **Fix task #124** — "Fix null pointer in checkout" — Fixes #123
+3. **QA task #125** — "Add regression test for empty cart checkout" — Related to #123
+
+Link QA task to bug so it's traceable; fix task handles the code change.
+
+---
+
+## Jira / Linear (Future Adapters)
+
+When adapters are added:
+
+| System | Link format |
+| ------ | ----------- |
+| **Jira** | `PROJ-123` in description; Jira auto-links |
+| **Linear** | `BUG-456` or `[Linear Issue](url)` |
+| **Azure DevOps** | `AB#123` for work item reference |
+
+For now, output markdown with explicit links; user can paste into Jira/Linear.

package/skills/qa-task-creator/references/task-types.md

@@ -0,0 +1,169 @@
+# Task Type Templates and Examples
+
+*Reference for classifying and structuring work tasks.*
+
+---
+
+## Development Tasks
+
+### Implement (new feature)
+
+**Template:**
+- **Title:** Implement [feature] in [component]
+- **Description:** Add [feature] per [spec/requirement reference]. [Context].
+- **Acceptance criteria:** [List of testable conditions]
+- **Labels:** `task`, `development`, `feature`
+
+**Example:**
+```
+Title: Implement email validation in UserRegistrationForm
+Description: Add client-side and server-side email validation per spec §3.2.
+Acceptance criteria:
+- Valid emails (RFC 5322) pass validation
+- Invalid formats show inline error message
+- Server returns 400 with error code for invalid email
+Labels: task, development, feature, frontend
+```
+
+### Fix (bug)
+
+**Template:**
+- **Title:** Fix [symptom] in [component]
+- **Description:** [Bug summary]. Fixes #[bug-number].
+- **Acceptance criteria:** [Conditions that verify fix]
+- **Labels:** `task`, `development`, `bug`
+
+**Example:**
+```
+Title: Fix null pointer when cart is empty in checkout
+Description: Checkout crashes when user proceeds with empty cart. Fixes #456.
+Acceptance criteria:
+- Empty cart shows "Add items to cart" message
+- Checkout button disabled when cart empty
+- No null pointer exceptions in checkout flow
+Labels: task, development, bug, checkout
+```
+
+### Refactor
+
+**Template:**
+- **Title:** Refactor [component] to [goal]
+- **Description:** [Current state] → [desired state]. [Rationale].
+- **Acceptance criteria:** [Behavior preserved; improvements verified]
+- **Labels:** `task`, `development`, `refactor`
+
+### Optimize
+
+**Template:**
+- **Title:** Optimize [operation] in [component]
+- **Description:** [Current performance] → [target]. [Approach].
+- **Acceptance criteria:** [Measurable performance criteria]
+- **Labels:** `task`, `development`, `performance`
+
+---
+
+## QA Tasks
+
+### Write tests
+
+**Template:**
+- **Title:** Add [test type] for [component/feature]
+- **Description:** [Coverage gap or risk]. [Scope].
+- **Acceptance criteria:** [Coverage target, scenarios covered]
+- **Labels:** `task`, `qa`, `testing`
+
+**Example:**
+```
+Title: Add unit tests for AuthService.login()
+Description: AuthService.login() has 0% coverage. High-risk authentication path.
+Acceptance criteria:
+- Happy path: valid credentials return token
+- Invalid credentials return 401
+- Locked account returns 423
+- Coverage ≥ 90% for AuthService
+Labels: task, qa, testing, auth
+```
+
+### Increase coverage
+
+**Template:**
+- **Title:** Increase test coverage for [module] to [target]%
+- **Description:** Current: [X]%. Target: [Y]%. Gaps: [list].
+- **Acceptance criteria:** [Coverage threshold; critical paths covered]
+- **Labels:** `task`, `qa`, `coverage`
+
+### Update test data
+
+**Template:**
+- **Title:** Update test data for [scenario]
+- **Description:** [What changed; why data needs update].
+- **Acceptance criteria:** [Data valid; tests pass]
+- **Labels:** `task`, `qa`, `test-data`
+
+---
+
+## Documentation Tasks
+
+### Update specs
+
+**Template:**
+- **Title:** Update [spec/doc] for [change]
+- **Description:** [What changed in implementation]. [Sections to update].
+- **Acceptance criteria:** [Spec reflects current behavior; examples updated]
+- **Labels:** `task`, `documentation`, `spec`
+
+### Add diagrams
+
+**Template:**
+- **Title:** Add [diagram type] for [topic]
+- **Description:** [Purpose]. [Scope]. Use qa-diagram-generator patterns.
+- **Acceptance criteria:** [Diagram accurate; embedded in doc]
+- **Labels:** `task`, `documentation`, `diagram`
+
+### API docs
+
+**Template:**
+- **Title:** Document [API/endpoint] in OpenAPI
+- **Description:** [Endpoint]. [Request/response]. [Examples].
+- **Acceptance criteria:** [OpenAPI valid; examples runnable]
+- **Labels:** `task`, `documentation`, `api`
+
+---
+
+## Enhancement Tasks
+
+### Performance
+
+**Template:**
+- **Title:** Improve [metric] for [component]
+- **Description:** [Current] → [target]. [Approach].
+- **Acceptance criteria:** [Benchmark before/after]
+- **Labels:** `task`, `enhancement`, `performance`
+
+### Validation
+
+**Template:**
+- **Title:** Add validation for [input/flow]
+- **Description:** [Gap]. [Validation rules].
+- **Acceptance criteria:** [Invalid inputs rejected; errors clear]
+- **Labels:** `task`, `enhancement`, `validation`
+
+### UI polish
+
+**Template:**
+- **Title:** Polish [UI element] for [improvement]
+- **Description:** [Current UX issue]. [Desired state].
+- **Acceptance criteria:** [Visual/UX criteria]
+- **Labels:** `task`, `enhancement`, `ui`
+
+---
+
+## Task Type Selection Matrix
+
+| Input Source | Primary Type | Secondary |
+| ------------ | ------------ | --------- |
+| Bug report | Development (fix) | QA (regression test) |
+| Coverage gap | QA (write tests) | Development (if implementation missing) |
+| Spec finding | Development / Documentation | QA |
+| Risk analysis | QA / Development | Documentation |
+| User request | Varies | — |

package/skills/qa-task-creator/templates/task-template.md

@@ -0,0 +1,24 @@
+# Task
+
+## [TASK-{ID}] {Title}
+
+**Type:** {Dev | QA | Docs | Enhancement}
+**Priority:** {P1 | P2 | P3 | P4}
+**Assignee:** {name or unassigned}
+**Estimate:** {story points or hours}
+
+## Description
+{Brief description of the task}
+
+## Acceptance Criteria
+- [ ] {Criterion 1}
+- [ ] {Criterion 2}
+- [ ] {Criterion 3}
+
+## Related Items
+- **Bug:** [BUG-{ID}]
+- **Requirement:** [REQ-{ID}]
+- **Coverage Gap:** {description}
+
+## Labels
+`type/{type}` `priority/{level}` `component/{name}`