qa-skills 3.0.0 → 3.1.0

package/skills/qa-changelog-analyzer/references/git-analysis-patterns.md

@@ -1,138 +0,0 @@
-# Git Diff Parsing Patterns
-
-## Overview
-
-Parse git diff output to extract changed files, classify change types, and map to modules. Used by qa-changelog-analyzer for impact analysis.
-
----
-
-## 1. Git Diff Commands
-
-### Staged Changes (Pre-Commit)
-
-```bash
-git diff --name-only --cached
-git diff --stat --cached
-```
-
-### Committed Changes
-
-```bash
-# Last commit
-git diff --name-only HEAD~1..HEAD
-
-# Last N commits
-git diff --name-only HEAD~5..HEAD
-
-# Specific commit range
-git diff --name-only abc123..def456
-```
-
-### Branch Comparison
-
-```bash
-# PR: feature branch vs main
-git diff --name-only origin/main...HEAD
-
-# Branch vs branch
-git diff --name-only base_branch..feature_branch
-```
-
-### With Rename Detection
-
-```bash
-git diff --name-only -M50% base..HEAD
-git diff --find-renames base..HEAD
-```
-
----
-
-## 2. Parsing Output
-
-### Name-Only Format
-
-```
-src/auth/login.ts
-src/auth/session.ts
-tests/auth/login.spec.ts
-config/env.example
-```
-
-- One path per line
-- Use `git status -s` for staged + unstaged with status prefix (`A`, `M`, `D`, `R`)
-
-### Stat Format
-
-```
- src/auth/login.ts   | 12 +++++----
- src/auth/session.ts |  5 +++++
- 2 files changed, 17 insertions(+), 4 deletions(-)
-```
-
-- Parse for file paths and change magnitude
-- Useful for prioritization (more changes = higher impact)
-
-### Change Type Detection
-
-| Git Status | Meaning | Action |
-|------------|---------|--------|
-| `A` or `??` (new) | Added | Need new tests |
-| `M` | Modified | Run existing; check for updates |
-| `D` | Deleted | Remove/update related tests |
-| `R` or `R100` | Renamed | Update imports in tests |
-
----
-
-## 3. File-to-Module Mapping
-
-### Directory-Based
-
-```
-src/auth/login.ts      → auth
-src/auth/session.ts    → auth
-src/api/users.ts       → api
-packages/core/utils.ts → core
-```
-
-- Use first path segment after `src/`, `packages/`, `lib/`, etc.
-- Configurable per project
-
-### Package/Import-Based (JS/TS)
-
-- Parse `package.json` name
-- Use import path: `@/auth` → auth
-- Monorepo: `packages/auth` → auth
-
-### Python
-
-- `src.auth.login` → auth
-- Directory: `src/auth/` → auth
-
-### Config Override
-
-- `impact-mapping.json` or `.qa-mapping` for custom mappings
-- Override automatic detection when structure is non-standard
-
----
-
-## 4. Exclusions
-
-Common exclusions from impact analysis:
-
-- `node_modules/`, `vendor/`, `__pycache__/`
-- Generated files: `*.generated.ts`, `dist/`, `build/`
-- Lock files: `package-lock.json`, `yarn.lock` (optional; may affect env)
-- Docs only: `*.md`, `docs/` (optional; no test impact)
-- Test files themselves: include in "tests to run" but not "modules affected"
-
----
-
-## 5. Edge Cases
-
-| Case | Handling |
-|------|----------|
-| Binary files | Skip or flag; no line-level analysis |
-| Submodule changes | Treat as config; may need integration tests |
-| Merge commits | Use `-m` or first parent; avoid duplicate counting |
-| Large diff | Summarize by module; avoid listing every file |
-| No git repo | Return error; require valid git context |

package/skills/qa-changelog-analyzer/references/impact-mapping.md

@@ -1,120 +0,0 @@
-# Mapping Code Changes to Test Recommendations
-
-## Overview
-
-Map code changes to concrete test recommendations: tests to run, tests to update, and tests to add. Used by qa-changelog-analyzer to produce actionable output.
-
----
-
-## 1. Tests to Run (Regression Scope)
-
-### Direct Mapping
-
-Changed file → tests that cover it:
-
-| Source | Method | Example |
-|--------|--------|---------|
-| Coverage report | Istanbul, JaCoCo, coverage.py | `auth/login.ts` → `login.spec.ts` |
-| Path convention | `tests/<module>/` or `*.spec.ts` | `auth/` → `tests/auth/*` |
-| Import grep | `import.*from.*auth` in tests | Find test files importing changed module |
-
-### Priority Levels
-
-- **Must run:** Direct unit/integration tests for changed modules
-- **Should run:** Integration tests that use changed APIs/components
-- **Optional:** Full suite, E2E, smoke (if risk threshold exceeded)
-
-### Downstream Impact
-
-- If `auth/session.ts` changed → check who imports it
-- API changes → integration tests for API consumers
-- DB schema → migration tests, repository tests
-
----
-
-## 2. Tests to Update
-
-### When Source Diverged
-
-- Assertions expect old behavior
-- Selectors target removed/changed elements
-- Mocks no longer match API shape
-
-### Detection Hints
-
-- Test file in same module as changed source
-- Test imports changed file
-- Test name suggests coverage of changed functionality
-
-### Recommendation Format
-
-```markdown
-- **tests/auth/login.spec.ts** — `login.ts` changed; verify assertions match new validation logic
-- **tests/api/users.integration.spec.ts** — `users.ts` response shape changed; update expectations
-```
-
----
-
-## 3. Tests to Add
-
-### New Files
-
-- New source file with no corresponding test
-- New module/component
-- New API endpoint
-
-### Uncovered Code Paths
-
-- New branches, error handlers, edge cases in modified files
-- Use coverage report: new lines with 0% coverage
-
-### Recommendation Format
-
-```markdown
-- **Add unit tests for** `src/auth/oauth.ts` — new file, no coverage
-- **Add integration test for** `POST /api/v2/users` — new endpoint
-```
-
----
-
-## 4. Tests to Remove
-
-### Deleted Source
-
-- Source file deleted → tests that only cover it are obsolete
-- Remove or repurpose tests
-
-### Deprecated Features
-
-- Feature removed → remove feature-specific tests
-- Keep shared setup/utilities if still used
-
----
-
-## 5. Config and Environment Changes
-
-| Change | Recommendation |
-|--------|----------------|
-| `.env`, `config/*` | Run env-specific tests; validate config loading |
-| `package.json`, `requirements.txt` | Run install + smoke; may affect dependencies |
-| CI config (`.github/`, `Jenkinsfile`) | Validate pipeline; run full suite once |
-| Dockerfile, k8s | Integration/E2E in target environment |
-
----
-
-## 6. Task Handoff to qa-task-creator
-
-Format suggestions for qa-task-creator:
-
-```markdown
-## Tasks
-
-1. **Add:** Unit tests for `src/auth/oauth.ts` (new file)
-2. **Update:** `tests/auth/login.spec.ts` — assertions for new validation
-3. **Remove:** `tests/legacy/deprecated.spec.ts` — source deleted
-4. **Run:** Regression scope (see Must Run list above)
-```
-
-- Each task is self-contained with file/module reference
-- Link to change impact report for context
-- Use labels: `qa`, `development`, `test-coverage`

package/skills/qa-clickup-integration/SKILL.md

@@ -1,166 +0,0 @@
----
-name: qa-clickup-integration
-description: ClickUp integration for creating tasks, managing lists/spaces, and tracking QA workflows via REST API.
-dependencies:
-  recommended:
-    - qa-bug-ticket-creator
-    - qa-task-creator
----
-
-# QA ClickUp Integration
-
-## Purpose
-
-Integrate QA workflow with ClickUp for task management. Create and manage tasks, lists, folders, and spaces; attach QA metadata via custom fields; and sync bug reports and work tasks from qa-bug-ticket-creator and qa-task-creator into ClickUp.
-
-## Primary Target
-
-**ClickUp** via REST API. Base URL: `https://api.clickup.com/api/v2`.
-
-## Features
-
-### Task Management
-
-| Feature | Description |
-| ------- | ----------- |
-| **Create tasks** | POST to list; set name, description, assignees, status, priority |
-| **Update tasks** | PUT to modify existing tasks |
-| **Get task** | GET task by ID for status checks |
-| **Subtasks** | Create subtasks for test steps or breakdown |
-| **Checklists** | Add checklist items for acceptance criteria |
-| **Attachments** | Attach screenshots, logs, HAR files |
-
-### Hierarchy
-
-| Level | API | Use |
-| ----- | --- | --- |
-| **Space** | GET /api/v2/team/{team_id}/space | QA workspace or project |
-| **Folder** | GET /api/v2/space/{space_id}/folder | Feature or module grouping |
-| **List** | GET /api/v2/folder/{folder_id}/list | Sprint, release, or backlog |
-| **Task** | POST /api/v2/list/{list_id}/task | Individual work item |
-
-### QA Metadata
-
-| Custom Field | Purpose |
-| ------------ | ------- |
-| **Severity** | Blocker / Critical / Major / Minor / Trivial |
-| **Test Type** | Unit / Integration / E2E / Performance / Security |
-| **Coverage** | Requirement or module coverage reference |
-| **Environment** | OS, browser, app version |
-| **Component** | Affected area (auth, checkout, API) |
-
-### Relationships
-
-- **Blocking** — Task A blocks Task B
-- **Waiting on** — Task A waits on Task B
-- **Linked** — Related tasks for traceability
-
-### Tags and Priorities
-
-- **Tags** — `bug`, `test-coverage`, `flaky`, `docs`, component tags
-- **Priority** — Urgent (1), High (2), Normal (3), Low (4)
-
-## Authentication
-
-| Variable | Description |
-| -------- | ----------- |
-| `CLICKUP_API_TOKEN` | Personal API token (starts with `pk_`) from .env |
-
-**Header:** `Authorization: <token>`
-
-Generate tokens at: ClickUp Settings → Apps → API Token.
-
-## Key API Endpoints
-
-| Method | Endpoint | Use |
-| ------ | -------- | --- |
-| POST | `/api/v2/list/{list_id}/task` | Create task |
-| GET | `/api/v2/task/{task_id}` | Get task details |
-| PUT | `/api/v2/task/{task_id}` | Update task |
-| GET | `/api/v2/team/{team_id}/space` | List spaces |
-| GET | `/api/v2/space/{space_id}/folder` | List folders |
-| GET | `/api/v2/folder/{folder_id}/list` | List lists |
-| POST | `/api/v2/task/{task_id}/attachment` | Add attachment |
-
-See `references/api-patterns.md` for request/response examples.
-
-## Integration with QA Skills
-
-| Skill | Integration |
-| ----- | ----------- |
-| **qa-bug-ticket-creator** | Create ClickUp tasks from bug reports; map severity, component, evidence |
-| **qa-task-creator** | Create ClickUp tasks from coverage gaps, spec findings, fix tasks |
-| **qa-test-reporter** | Attach test reports as task attachments; link failures to tasks |
-
-### Handoff Flow
-
-1. **Bug report** → qa-bug-ticket-creator structures report → qa-clickup-integration creates task in target list
-2. **Fix task** → qa-task-creator generates task → qa-clickup-integration creates task, links to bug task
-3. **Coverage gap** → qa-coverage-analyzer output → qa-task-creator → qa-clickup-integration
-
-## Trigger Phrases
-
-- "Create ClickUp task from [bug report / test failure]"
-- "Add task to ClickUp list [name]"
-- "Sync bug to ClickUp with severity and evidence"
-- "Create ClickUp task from coverage gap"
-- "Link fix task to bug in ClickUp"
-- "Attach screenshot to ClickUp task [id]"
-- "Get ClickUp task status for [id]"
-
-## Workflow
-
-1. **Input** — Bug report, task description, coverage gap, or user request
-2. **Resolve target** — Team ID, Space, Folder, List (from user or config)
-3. **Map fields** — Map QA fields to ClickUp task fields per `references/field-mapping.md`
-4. **Create/update** — POST or PUT via REST API
-5. **Attach** — Add screenshots, logs when provided
-6. **Link** — Set blocking/waiting-on when paired with bug or fix task
-
-## Scope
-
-**Can do (autonomous):**
-- Create and update tasks in specified lists
-- Map severity, priority, component, test type to ClickUp fields
-- Add subtasks, checklists, attachments
-- Set task relationships (blocking, waiting on)
-- Resolve space/folder/list from user input or config
-- Integrate with qa-bug-ticket-creator and qa-task-creator output
-
-**Cannot do (requires confirmation):**
-- Create spaces, folders, or lists (assume they exist)
-- Override user-specified list or assignee
-- Set custom fields without workspace configuration
-
-**Will not do (out of scope):**
-- Modify production or test code
-- Delete tasks or archives (user responsibility)
-- Create ClickUp workspaces or teams
-
-## Quality Checklist
-
-- [ ] Task includes name, description, and appropriate priority
-- [ ] QA metadata (severity, test type, component) mapped per field-mapping
-- [ ] Attachments added when evidence provided
-- [ ] No hardcoded secrets; token from .env
-- [ ] List ID resolved before create; task ID validated before update
-- [ ] Relationships set when linking bug to fix task
-- [ ] Error handling for 401, 404, 429 (rate limit)
-
-## Troubleshooting
-
-| Symptom | Likely Cause | Fix |
-| ------- | ------------ | --- |
-| 401 Unauthorized | Token missing or invalid | Check `CLICKUP_API_TOKEN` in .env; regenerate if expired |
-| 404 Not Found | Invalid list_id or task_id | Verify IDs; use GET to list spaces/folders/lists |
-| 429 Rate limit | Too many requests | Implement backoff; batch operations |
-| Custom field not applied | Field ID wrong or not configured | Check workspace custom fields; use correct field ID |
-| Attachment fails | File size or format | ClickUp limits; use supported formats (png, jpg, txt, etc.) |
-| Wrong list | List ID from wrong folder | Resolve full hierarchy: team → space → folder → list |
-
-## Reference Files
-
-| Topic | File |
-| ----- | ---- |
-| API patterns: tasks, lists, spaces, custom fields | `references/api-patterns.md` |
-| Mapping QA fields to ClickUp task fields | `references/field-mapping.md` |

package/skills/qa-clickup-integration/references/api-patterns.md

@@ -1,102 +0,0 @@
-# ClickUp API Patterns
-
-## Base URL and Auth
-
-```
-Base: https://api.clickup.com/api/v2
-Header: Authorization: <CLICKUP_API_TOKEN>
-Content-Type: application/json
-```
-
-## Hierarchy Resolution
-
-1. **Team** — `GET /api/v2/team` returns teams; use `team_id` for spaces
-2. **Space** — `GET /api/v2/team/{team_id}/space` returns spaces
-3. **Folder** — `GET /api/v2/space/{space_id}/folder` returns folders (archived: false)
-4. **List** — `GET /api/v2/folder/{folder_id}/list` returns lists
-
-## Create Task
-
-**POST** `/api/v2/list/{list_id}/task`
-
-```json
-{
-  "name": "Login fails when password contains special chars",
-  "description": "**Expected:** User can log in with special chars in password.\n**Actual:** 500 error.\n**Steps:** 1. Go to /login 2. Enter user@test.com + pass!@# 3. Submit",
-  "assignees": [12345],
-  "tags": ["bug", "auth"],
-  "status": "to do",
-  "priority": 2,
-  "due_date": 1709856000000,
-  "custom_task_ids": false,
-  "notify_all": false
-}
-```
-
-**Response:** Task object with `id`, `url`, `status`, etc.
-
-## Get Task
-
-**GET** `/api/v2/task/{task_id}`
-
-Returns full task including custom fields, subtasks, checklists.
-
-## Update Task
-
-**PUT** `/api/v2/task/{task_id}`
-
-Same body shape as create; only include fields to update.
-
-## Custom Fields
-
-Custom fields are workspace-specific. Use `GET /api/v2/list/{list_id}/field` to list available fields.
-
-Example custom field in task:
-```json
-{
-  "custom_fields": [
-    {
-      "id": "abc123",
-      "value": "Critical"
-    }
-  ]
-}
-```
-
-## Subtasks
-
-Create subtask: **POST** `/api/v2/list/{list_id}/task` with `parent` set to parent task ID.
-
-Or add via task update with subtasks array.
-
-## Checklists
-
-**POST** `/api/v2/task/{task_id}/checklist`
-
-```json
-{
-  "name": "Acceptance Criteria",
-  "items": [
-    { "name": "User can log in with special chars" },
-    { "name": "Error message is user-friendly" }
-  ]
-}
-```
-
-## Attachments
-
-**POST** `/api/v2/task/{task_id}/attachment`
-
-`Content-Type: multipart/form-data` with file.
-
-Supported: png, jpg, gif, pdf, txt, log, har, etc.
-
-## Task Relationships
-
-- **Linked tasks** — Use `linking` in task body or separate linking API
-- **Blocking** — Set via custom workflow or dependency field if configured
-
-## Rate Limits
-
-- Typical: 100 requests per minute per token
-- 429 response: retry with exponential backoff

package/skills/qa-clickup-integration/references/field-mapping.md

@@ -1,71 +0,0 @@
-# QA Field to ClickUp Mapping
-
-## Standard Task Fields
-
-| QA Field | ClickUp Field | Notes |
-| -------- | ------------- | ----- |
-| Title | `name` | Direct mapping |
-| Description | `description` | Markdown supported |
-| Severity | `priority` or custom | 1=Urgent, 2=High, 3=Normal, 4=Low |
-| Priority (P1–P5) | `priority` | P1→1, P2→2, P3→3, P4/P5→4 |
-| Component | `tags` | Add as tag, e.g. `auth`, `checkout` |
-| Assignee | `assignees` | Array of member IDs |
-| Due date | `due_date` | Unix ms |
-| Status | `status` | Must match list status names |
-
-## QA-Specific → ClickUp Custom Fields
-
-Configure these custom fields in your ClickUp workspace, then map by field ID:
-
-| QA Field | Custom Field Type | Example Value |
-| -------- | ----------------- | ------------- |
-| Severity (ISO) | Dropdown | Blocker, Critical, Major, Minor, Trivial |
-| Test Type | Dropdown | Unit, Integration, E2E, Performance, Security |
-| Coverage | Text/URL | Requirement ID or module path |
-| Environment | Text | "Chrome 120, Windows 11, v2.1.0" |
-| Expected Result | Long text | From bug report template |
-| Actual Result | Long text | From bug report template |
-| Steps to Reproduce | Long text | Numbered steps |
-| Evidence | Attachment | Screenshots, logs via attachment API |
-
-## Bug Report Template Mapping
-
-| Bug Report Field | ClickUp Target |
-| ---------------- | -------------- |
-| Title | `name` |
-| Expected Result | `description` or custom field |
-| Actual Result | `description` or custom field |
-| Steps to Reproduce | `description` or checklist |
-| Environment | Custom field or `description` |
-| Evidence | Attachments |
-| Severity | `priority` + custom field |
-| Priority | `priority` |
-| Component/Module | `tags` |
-
-## Task Creator Output Mapping
-
-| Task Field | ClickUp Target |
-| ---------- | -------------- |
-| Title | `name` |
-| Description | `description` |
-| Acceptance criteria | Checklist |
-| Labels (task, qa, component) | `tags` |
-| Links (Fixes #N) | `description` (inline) or custom URL field |
-| Task type | `tags` (e.g. `development`, `qa`, `documentation`) |
-
-## Tag Conventions
-
-| QA Source | Suggested Tags |
-| --------- | --------------- |
-| Bug | `bug`, `{component}` |
-| Coverage gap | `test-coverage`, `{component}` |
-| Flaky test | `flaky`, `{component}` |
-| Fix task | `fix`, `development` |
-| QA task | `qa`, `testing` |
-| Documentation | `docs`, `documentation` |
-
-## Resolving Field IDs
-
-1. Use ClickUp API: `GET /api/v2/list/{list_id}/field`
-2. Or: Workspace Settings → Custom Fields → copy field ID from URL or API
-3. Store mapping in config or pass via user input for workspace-specific setups