ai-qakit 1.0.0

package/templates/.claude/commands/qakit/scout.md

@@ -0,0 +1,195 @@
+# Scout Test Codebase
+
+Fast parallel search across test codebase to find tests, page objects, fixtures, and patterns.
+
+## Usage
+
+```
+/qakit:scout [search-description] [scale]
+```
+
+## Arguments
+
+| Argument | Description |
+|----------|-------------|
+| `search-description` | What to search for in test codebase |
+| `scale` | Search depth 1-5 (default: 2) |
+
+## Scale Guide
+
+| Scale | Description | Use Case |
+|-------|-------------|----------|
+| 1 | Quick single search | Find specific test file |
+| 2 | Standard parallel (default) | Find related tests |
+| 3 | Comprehensive search | Find all test patterns |
+| 4 | Deep search | Full test architecture |
+| 5 | Exhaustive | Complete test inventory |
+
+## Examples
+
+```bash
+/qakit:scout "login tests" 1
+/qakit:scout "authentication page objects" 2
+/qakit:scout "API test patterns" 3
+/qakit:scout "all checkout flow tests" 4
+```
+
+## Instructions
+
+### Step 1: Parse Arguments
+
+Extract search description and scale from $ARGUMENTS:
+- Default scale: 2
+- Validate scale is 1-5
+
+### Step 2: Define Search Zones
+
+Based on scale, divide test codebase into zones:
+
+**Scale 1 (Quick):**
+- Single zone: Direct file/pattern match
+
+**Scale 2 (Standard):**
+- Zone A: Test specs (`*.spec.ts`, `*.test.ts`)
+- Zone B: Page Objects (`pages/`, `pageobjects/`)
+
+**Scale 3 (Comprehensive):**
+- Zone A: Test specs
+- Zone B: Page Objects
+- Zone C: Fixtures and helpers
+
+**Scale 4 (Deep):**
+- Zone A: Test specs
+- Zone B: Page Objects
+- Zone C: Fixtures and helpers
+- Zone D: Config and setup files
+
+**Scale 5 (Exhaustive):**
+- All zones + documentation + reports
+
+### Step 3: Execute Parallel Search
+
+For each zone, search using:
+
+```bash
+# Find test files
+find . -type f \( -name "*.spec.ts" -o -name "*.test.ts" \) | head -50
+
+# Search in test files
+grep -rn "[search-term]" --include="*.spec.ts" --include="*.test.ts" | head -30
+
+# Find page objects
+find . -path "*/pages/*" -name "*.ts" | head -30
+
+# Search in page objects
+grep -rn "[search-term]" --include="*Page.ts" --include="*page.ts" | head -30
+
+# Find fixtures
+find . -path "*/fixtures/*" -o -path "*/data/*" -name "*.ts" | head -20
+```
+
+### Step 4: Categorize Results
+
+Organize findings by category:
+
+```
+════════════════════════════════════════════════════════════════════
+                    🔍 SCOUT REPORT: [search-term]
+════════════════════════════════════════════════════════════════════
+
+SEARCH PARAMETERS:
+  Query: [search-description]
+  Scale: [scale]/5
+  Zones Searched: [count]
+
+📊 RESULTS SUMMARY:
+  Total Matches: [count]
+  Test Files: [count]
+  Page Objects: [count]
+  Fixtures: [count]
+  Helpers: [count]
+
+════════════════════════════════════════════════════════════════════
+                    📁 TEST SPECS
+════════════════════════════════════════════════════════════════════
+
+HIGH RELEVANCE:
+  • tests/e2e/login.spec.ts (line 45) - "login with valid credentials"
+  • tests/e2e/auth.spec.ts (line 23) - "authentication flow"
+
+MODERATE RELEVANCE:
+  • tests/integration/user.spec.ts (line 12) - "user session"
+
+════════════════════════════════════════════════════════════════════
+                    📄 PAGE OBJECTS
+════════════════════════════════════════════════════════════════════
+
+  • pages/LoginPage.ts - Login page interactions
+  • pages/AuthPage.ts - Authentication helpers
+
+════════════════════════════════════════════════════════════════════
+                    🔧 FIXTURES & HELPERS
+════════════════════════════════════════════════════════════════════
+
+  • fixtures/auth.fixture.ts - Authentication setup
+  • helpers/api.helper.ts - API utilities
+
+════════════════════════════════════════════════════════════════════
+                    💡 KEY INSIGHTS
+════════════════════════════════════════════════════════════════════
+
+  • Found [X] tests covering [feature]
+  • Page Object pattern used consistently
+  • [Y] fixtures available for test data
+
+════════════════════════════════════════════════════════════════════
+                    ❓ UNRESOLVED
+════════════════════════════════════════════════════════════════════
+
+  • No tests found for [gap area]
+  • Missing page object for [component]
+
+════════════════════════════════════════════════════════════════════
+```
+
+### Step 5: Provide Recommendations
+
+Based on findings:
+- Suggest related tests to review
+- Identify coverage gaps
+- Recommend next actions
+
+## Search Patterns
+
+### Common QA Searches
+
+| Search | What it finds |
+|--------|---------------|
+| `"login"` | Login-related tests and pages |
+| `"API test"` | API test patterns |
+| `"fixture"` | Test data fixtures |
+| `"flaky"` | Potentially flaky tests |
+| `"skip"` | Skipped tests |
+| `"todo"` | Incomplete tests |
+| `"data-testid"` | Selector usage |
+| `"waitFor"` | Wait patterns |
+
+### Framework-Specific
+
+| Framework | Search Pattern |
+|-----------|----------------|
+| Playwright | `test(`, `expect(`, `page.` |
+| WebdriverIO | `it(`, `browser.`, `$()` |
+| Cypress | `cy.`, `describe(` |
+| Jest | `test(`, `describe(`, `expect(` |
+
+## Output
+
+Scout report with:
+- Categorized results by relevance
+- File locations with line numbers
+- Key insights and patterns found
+- Coverage gaps identified
+- Recommended next actions
+
+$ARGUMENTS

package/templates/.claude/commands/qakit/setup/confluence.md

@@ -0,0 +1,140 @@
+# Setup Confluence Integration
+
+Configure Confluence REST API access for fetching documentation pages.
+
+## Usage
+
+```
+/qakit:setup/confluence
+```
+
+## Quick Setup
+
+### Step 1: API Token
+
+Use the same Atlassian API token as Jira (same account):
+- Token: https://id.atlassian.com/manage-profile/security/api-tokens
+
+### Step 2: Set Environment Variables
+
+Add to `.env.local` or shell profile:
+
+```bash
+# Confluence Configuration (can reuse Jira credentials)
+export CONFLUENCE_BASE_URL="https://yourcompany.atlassian.net"
+export CONFLUENCE_EMAIL="$JIRA_EMAIL"
+export CONFLUENCE_API_TOKEN="$JIRA_API_TOKEN"
+```
+
+Or if separate instance:
+```bash
+export CONFLUENCE_BASE_URL="https://confluence.yourcompany.com"
+export CONFLUENCE_EMAIL="your.email@company.com"
+export CONFLUENCE_API_TOKEN="your-token"
+```
+
+### Step 3: Test Connection
+
+```bash
+# Source env vars
+source .env.local
+
+# Test API access
+curl -s -u "$CONFLUENCE_EMAIL:$CONFLUENCE_API_TOKEN" \
+  "$CONFLUENCE_BASE_URL/wiki/api/v2/spaces?limit=5" | jq '.results[].name'
+```
+
+Should list your Confluence spaces.
+
+## Environment Variables
+
+| Variable | Required | Description |
+|----------|----------|-------------|
+| `CONFLUENCE_BASE_URL` | Yes | Confluence URL (no trailing slash) |
+| `CONFLUENCE_EMAIL` | Yes | Atlassian account email |
+| `CONFLUENCE_API_TOKEN` | Yes | API token |
+
+## Example .env.local
+
+```bash
+#!/bin/bash
+# Atlassian Configuration (Jira + Confluence)
+
+# Base URLs
+export JIRA_BASE_URL="https://yourcompany.atlassian.net"
+export CONFLUENCE_BASE_URL="https://yourcompany.atlassian.net"
+
+# Credentials (shared)
+export JIRA_EMAIL="your.email@company.com"
+export JIRA_API_TOKEN="ATATT3xFfGF0..."
+
+# Confluence uses same credentials
+export CONFLUENCE_EMAIL="$JIRA_EMAIL"
+export CONFLUENCE_API_TOKEN="$JIRA_API_TOKEN"
+```
+
+## Useful API Endpoints
+
+### List Spaces
+```bash
+curl -s -u "$CONFLUENCE_EMAIL:$CONFLUENCE_API_TOKEN" \
+  "$CONFLUENCE_BASE_URL/wiki/api/v2/spaces"
+```
+
+### Get Page by ID
+```bash
+curl -s -u "$CONFLUENCE_EMAIL:$CONFLUENCE_API_TOKEN" \
+  "$CONFLUENCE_BASE_URL/wiki/api/v2/pages/123456?body-format=storage"
+```
+
+### Search Pages
+```bash
+curl -s -u "$CONFLUENCE_EMAIL:$CONFLUENCE_API_TOKEN" \
+  "$CONFLUENCE_BASE_URL/wiki/rest/api/content/search?cql=space=PROJ+AND+title~\"Test\""
+```
+
+### Get Page by Title
+```bash
+curl -s -u "$CONFLUENCE_EMAIL:$CONFLUENCE_API_TOKEN" \
+  "$CONFLUENCE_BASE_URL/wiki/rest/api/content?spaceKey=PROJ&title=Test%20Plan"
+```
+
+## Troubleshooting
+
+### "401 Unauthorized"
+- Verify email matches Atlassian account
+- Regenerate API token
+- Check token hasn't expired
+
+### "403 Forbidden"
+- Check space permissions
+- Verify API access is enabled
+
+### "404 Not Found"
+- Check CONFLUENCE_BASE_URL format
+- Verify page/space exists
+- Check you have view permission
+
+### Different Confluence Instance
+If Confluence is separate from Jira:
+```bash
+# Jira Cloud
+export JIRA_BASE_URL="https://company.atlassian.net"
+
+# Confluence Server (on-premise)
+export CONFLUENCE_BASE_URL="https://confluence.company.com"
+export CONFLUENCE_EMAIL="username"  # Not email for Server
+export CONFLUENCE_API_TOKEN="personal-access-token"
+```
+
+## Integration with Commands
+
+Once configured:
+
+| Command | Description |
+|---------|-------------|
+| `/qakit:confluence/fetch` | Fetch page content |
+| `/qakit:confluence/search` | Search for docs |
+| `/qakit:jira/analyze` | Auto-fetches linked Confluence docs |
+
+$ARGUMENTS

package/templates/.claude/commands/qakit/setup/jira.md

@@ -0,0 +1,154 @@
+# Setup Jira Integration
+
+Configure Jira REST API access for fetching tickets into feature specs.
+
+## Usage
+
+```
+/qakit:setup/jira
+```
+
+## Quick Setup
+
+### Step 1: Generate API Token
+
+1. Go to https://id.atlassian.com/manage-profile/security/api-tokens
+2. Click "Create API token"
+3. Give it a label (e.g., "AI QAKit")
+4. Copy the token (you won't see it again!)
+
+### Step 2: Set Environment Variables
+
+Add to your `.env.local` or shell profile (`.zshrc`, `.bashrc`):
+
+```bash
+# Jira Configuration
+export JIRA_BASE_URL="https://yourcompany.atlassian.net"
+export JIRA_EMAIL="your.email@company.com"
+export JIRA_API_TOKEN="your-api-token-here"
+```
+
+### Step 3: Test Connection
+
+```bash
+# Source env vars
+source .env.local
+
+# Test API access
+curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
+  "$JIRA_BASE_URL/rest/api/3/myself" | jq '.displayName'
+```
+
+Should output your Jira display name.
+
+## Environment Variables
+
+| Variable | Required | Description |
+|----------|----------|-------------|
+| `JIRA_BASE_URL` | Yes | Your Jira instance URL (no trailing slash) |
+| `JIRA_EMAIL` | Yes | Your Atlassian account email |
+| `JIRA_API_TOKEN` | Yes | API token from Atlassian |
+
+## Example .env.local
+
+```bash
+#!/bin/bash
+# Jira Configuration
+# NEVER commit actual values to version control!
+
+export JIRA_BASE_URL="https://yourcompany.atlassian.net"
+export JIRA_EMAIL="your.email@company.com"
+export JIRA_API_TOKEN="ATATT3xFfGF0..."
+```
+
+## Useful API Endpoints
+
+### Get Issue Details
+```bash
+curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
+  "$JIRA_BASE_URL/rest/api/3/issue/PROJ-123"
+```
+
+### Search Issues (JQL)
+```bash
+curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
+  "$JIRA_BASE_URL/rest/api/3/search?jql=project=PROJ+AND+status=Open"
+```
+
+### List Projects
+```bash
+curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
+  "$JIRA_BASE_URL/rest/api/3/project"
+```
+
+### Get Issue Comments
+```bash
+curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
+  "$JIRA_BASE_URL/rest/api/3/issue/PROJ-123/comment"
+```
+
+## Jira Cloud vs Server
+
+### Jira Cloud (Atlassian hosted)
+- URL format: `https://yourcompany.atlassian.net`
+- Auth: Email + API Token
+- Token: https://id.atlassian.com/manage-profile/security/api-tokens
+
+### Jira Server (Self-hosted)
+- URL format: `https://jira.yourcompany.com`
+- Auth: Username + Personal Access Token
+- Token: Jira → Profile → Personal Access Tokens
+
+## Troubleshooting
+
+### "401 Unauthorized"
+- Verify JIRA_EMAIL matches your Atlassian account
+- Regenerate API token
+- Check token hasn't expired
+
+### "403 Forbidden"
+- Your account may not have API access
+- Contact Jira admin to enable API access
+
+### "404 Not Found"
+- Check JIRA_BASE_URL is correct (no trailing slash)
+- Verify the ticket/project exists
+- Ensure you have permission to view the resource
+
+### Connection Timeout
+- Check if VPN is required
+- Verify URL is accessible: `curl -I $JIRA_BASE_URL`
+
+## Security Best Practices
+
+1. **Never commit tokens** - Use `.env.local` (gitignored)
+2. **Use read-only scope** - API tokens have full access, be careful
+3. **Rotate tokens regularly** - Every 90 days recommended
+4. **Use per-project tokens** - Create separate tokens for different projects
+
+## Integration with Commands
+
+Once configured, these commands can fetch Jira data:
+
+| Command | Description |
+|---------|-------------|
+| `/qakit:feature/from-jira PROJ-123` | Create feature spec from ticket |
+| `/qakit:test/from-jira PROJ-123` | Generate test cases from ticket |
+
+## Example Workflow
+
+```bash
+# 1. Setup (one-time)
+/qakit:setup/jira
+
+# 2. Create feature from Jira ticket
+/qakit:feature/from-jira LG-4018
+
+# 3. Enrich with additional context
+/qakit:feature/enrich docs/features/LG-4018.md --ui
+
+# 4. Generate test cases
+/qakit:test/create-test-case docs/features/LG-4018.md
+```
+
+$ARGUMENTS

package/templates/.claude/commands/qakit/spec/analyze.md

@@ -0,0 +1,46 @@
+# Analyze Requirements for Testing
+
+Analyze requirements to identify testing needs.
+
+## Usage
+```
+/qakit:spec/analyze <requirements-file>
+```
+
+## Instructions
+
+1. **Parse Requirements**
+   - Read requirement document
+   - Identify functional requirements
+   - Identify non-functional requirements
+
+2. **Testability Analysis**
+   For each requirement:
+   - Is it testable?
+   - What type of test?
+   - What's the complexity?
+
+3. **Generate Analysis Report**
+   ```markdown
+   # Requirements Analysis
+   
+   ## Summary
+   - Total requirements: X
+   - Testable: Y
+   - Not testable: Z
+   
+   ## By Test Type
+   | Type | Count |
+   |------|-------|
+   | Unit | 15 |
+   | Integration | 8 |
+   | E2E | 5 |
+   | Manual | 3 |
+   
+   ## Risk Assessment
+   | Requirement | Risk | Priority |
+   |-------------|------|----------|
+   | REQ-001 | High | P1 |
+   ```
+
+$ARGUMENTS