ai-qakit 1.0.0

package/templates/.claude/commands/qakit/bug/investigate.md

@@ -0,0 +1,96 @@
+# Investigate Bug
+
+Investigate a bug to find root cause and potential fixes.
+
+## Usage
+
+```
+/qakit:bug/investigate <bug-description-or-id>
+```
+
+## Instructions
+
+Investigate the bug systematically:
+
+1. **Gather Information**
+   - Read bug description/ticket
+   - Identify affected components
+   - Note reproduction steps if available
+
+2. **Analyze Symptoms**
+   - What is the expected behavior?
+   - What is the actual behavior?
+   - When did it start occurring?
+   - What changed recently?
+
+3. **Trace the Issue**
+   - Search codebase for related code
+   - Check recent commits in affected areas
+   - Review error logs if available
+   - Identify data flow path
+
+4. **Root Cause Analysis**
+   Use the 5 Whys technique:
+   ```
+   Problem: <observed issue>
+   Why 1: <first level cause>
+   Why 2: <second level cause>
+   Why 3: <third level cause>
+   Why 4: <fourth level cause>
+   Why 5: <root cause>
+   ```
+
+5. **Generate Investigation Report**
+   ```markdown
+   # Bug Investigation Report
+   
+   ## Bug Summary
+   - **ID**: <bug-id>
+   - **Title**: <bug-title>
+   - **Severity**: Critical/High/Medium/Low
+   - **Status**: Investigating
+   
+   ## Symptoms
+   - <symptom-1>
+   - <symptom-2>
+   
+   ## Affected Components
+   - `<file-path-1>`
+   - `<file-path-2>`
+   
+   ## Root Cause Analysis
+   <detailed-analysis>
+   
+   ## Potential Fixes
+   1. **Option A**: <fix-description>
+      - Pros: ...
+      - Cons: ...
+      - Risk: Low/Medium/High
+   
+   2. **Option B**: <fix-description>
+      - Pros: ...
+      - Cons: ...
+      - Risk: Low/Medium/High
+   
+   ## Recommended Fix
+   <recommended-approach>
+   
+   ## Test Plan
+   - <test-to-verify-fix>
+   
+   ## Prevention
+   - <how-to-prevent-similar-bugs>
+   ```
+
+6. **Suggest Related Tests**
+   - Unit tests to add
+   - Integration tests to add
+   - Regression tests needed
+
+## Output
+
+- Investigation report in markdown
+- Suggested code changes
+- Test recommendations
+
+$ARGUMENTS

package/templates/.claude/commands/qakit/bug/report.md

@@ -0,0 +1,147 @@
+# Create Bug Report
+
+Create a detailed bug report following Enouvo QA standards.
+
+## Usage
+
+```
+/qakit:bug/report <issue-description>
+```
+
+## Instructions
+
+Create a comprehensive bug report by following these steps:
+
+### 1. Generate Bug Title
+
+**Use the pattern**: `[Category] Problem - Action - Location`
+
+| Category | Use When |
+|----------|----------|
+| `[Functionality]` | Feature doesn't work as expected |
+| `[UI]` | Visual/layout issues |
+| `[Performance]` | Slow response, timeout |
+| `[Security]` | Security vulnerabilities |
+| `[Data]` | Data corruption, incorrect data |
+| `[API]` | API response issues |
+| `[Crash]` | Application crashes |
+| `[Compatibility]` | Browser/device specific issues |
+
+**Examples**:
+- ✅ `[Functionality] Error - Unable to Log In - Login Page`
+- ✅ `[UI] Button Misaligned - Click "Save" - Settings Page`
+- ✅ `[API] 500 Error - Submit Form - Registration Page`
+- ❌ `Login doesn't work` (too vague)
+
+### 2. Generate Bug Report Structure
+
+```markdown
+# Bug Report: [BUG-MODULE-XXX]
+
+## Summary
+
+| Field | Value |
+|-------|-------|
+| **Bug ID** | BUG-MODULE-XXX |
+| **Title** | [Category] Problem - Action - Location |
+| **Module / Feature** | [Feature name] |
+| **Severity** | Critical / Major / Minor / Low |
+| **Priority** | Urgent / High / Normal / Low |
+| **Status** | New |
+| **Reporter** | [Your name] |
+| **Assigned To** | [Developer name or TBD] |
+| **Related Test Case** | [TC-XXX if applicable] |
+
+## Environment
+
+| Field | Value |
+|-------|-------|
+| **Environment** | Staging / Production |
+| **URL** | [URL where bug occurred] |
+| **Browser** | [Browser name and version] |
+| **OS** | [Operating system] |
+| **Device** | [Device type if mobile] |
+| **App Version** | [Version number] |
+
+## Preconditions
+
+1. [Precondition 1]
+2. [Precondition 2]
+
+## Steps to Reproduce
+
+1. [Step 1]
+2. [Step 2]
+3. [Step 3]
+
+## Results
+
+| Field | Value |
+|-------|-------|
+| **Expected Result** | [What should happen] |
+| **Actual Result** | [What actually happens] |
+
+## Evidence
+
+- Screenshot: [link or filename]
+- Video: [link if available]
+- Console Log: [error message if any]
+- API Response: [response body if applicable]
+
+## Additional Information
+
+- **Reproducibility**: Always / Sometimes / Rarely
+- **Workaround**: [Workaround if available]
+- **Notes**: [Any additional context]
+```
+
+### 3. Classify Severity
+
+| Severity | Definition | Examples |
+|----------|------------|----------|
+| **Critical** | System crash, data loss, security breach | App crashes, data corruption |
+| **Major** | Key feature broken, no workaround | Cannot checkout, search fails |
+| **Minor** | Feature issue with workaround | Filter doesn't persist |
+| **Low** | Cosmetic, typo, minor UI | Button misaligned |
+
+### 4. Classify Priority
+
+| Priority | Definition | Response Time |
+|----------|------------|---------------|
+| **Urgent** | Blocks release, affects production | Fix immediately |
+| **High** | Major functionality affected | Fix within 24-48 hours |
+| **Normal** | Standard defect | Fix within sprint |
+| **Low** | Minor issue | Fix when time permits |
+
+### 5. Include Evidence
+
+- Screenshots of the issue
+- Console logs (F12 → Console)
+- Network requests (F12 → Network)
+- API response body
+- Video recording for complex flows
+
+### 6. Bug Lifecycle
+
+```
+New → Assigned → In Progress → Ready for QA → Verified → Closed
+                     ↓                            ↓
+                  Reopened ←──────────────────────┘
+```
+
+## Output Location
+
+Save bug report to: `bugs/[MODULE]/BUG-MODULE-XXX.md`
+
+## Quality Checklist
+
+Before submitting, verify:
+
+- [ ] Title follows pattern: `[Category] Problem - Action - Location`
+- [ ] Steps are specific and reproducible
+- [ ] Environment details are complete
+- [ ] Evidence is attached
+- [ ] Severity/Priority are appropriate
+- [ ] Related test case is linked (if applicable)
+
+$ARGUMENTS

package/templates/.claude/commands/qakit/bug/reproduce.md

@@ -0,0 +1,101 @@
+# Create Reproduction Steps
+
+Create detailed reproduction steps for a bug.
+
+## Usage
+
+```
+/qakit:bug/reproduce <bug-description>
+```
+
+## Instructions
+
+Create clear reproduction steps:
+
+1. **Analyze the Bug**
+   - Understand the reported issue
+   - Identify the user flow involved
+   - Determine preconditions
+
+2. **Create Minimal Reproduction**
+   - Find the shortest path to reproduce
+   - Identify required data/state
+   - Note environment requirements
+
+3. **Generate Reproduction Guide**
+   ```markdown
+   # Bug Reproduction Guide
+   
+   ## Bug Reference
+   - **Bug ID**: <id>
+   - **Title**: <title>
+   
+   ## Prerequisites
+   - [ ] <prerequisite-1>
+   - [ ] <prerequisite-2>
+   
+   ## Test Data Required
+   | Data | Value | Notes |
+   |------|-------|-------|
+   | User | test@example.com | Must have admin role |
+   | ... | ... | ... |
+   
+   ## Environment Setup
+   1. <setup-step-1>
+   2. <setup-step-2>
+   
+   ## Reproduction Steps
+   
+   ### Step 1: <action>
+   - Navigate to: `<url>`
+   - Expected state: <what-you-should-see>
+   
+   ### Step 2: <action>
+   - Click on: `<element>`
+   - Input: `<value>`
+   - Expected state: <what-you-should-see>
+   
+   ### Step 3: <action>
+   - <action-description>
+   - **BUG OCCURS HERE**
+   
+   ## Expected Result
+   <what-should-happen>
+   
+   ## Actual Result
+   <what-actually-happens>
+   
+   ## Reproduction Rate
+   - [ ] 100% - Always reproducible
+   - [ ] 75%+ - Usually reproducible
+   - [ ] 50% - Sometimes reproducible
+   - [ ] <50% - Rarely reproducible
+   
+   ## Variations Tested
+   | Variation | Result |
+   |-----------|--------|
+   | Different browser | Same issue |
+   | Different user | Works fine |
+   | ... | ... |
+   
+   ## Minimal Test Case
+   ```typescript
+   // Code to reproduce programmatically
+   test('reproduces bug', async () => {
+     // Setup
+     // Action
+     // Assert bug behavior
+   });
+   ```
+   ```
+
+4. **Create Automated Reproduction**
+   - E2E test that reproduces the bug
+   - Can be used for regression testing after fix
+
+## Output
+
+- Detailed reproduction guide
+- Automated test case (optional)
+
+$ARGUMENTS

package/templates/.claude/commands/qakit/bug/triage.md

@@ -0,0 +1,101 @@
+# Triage Bugs
+
+Triage and prioritize bugs for resolution.
+
+## Usage
+
+```
+/qakit:bug/triage [bug-list-or-query]
+```
+
+## Instructions
+
+Triage bugs systematically:
+
+1. **Gather Bug List**
+   - Read provided bug list or query
+   - Fetch from issue tracker if integrated
+   - Group by component/feature
+
+2. **Assess Each Bug**
+   For each bug, evaluate:
+   
+   **Severity Assessment**
+   - Critical: System down, data loss, security breach
+   - High: Major feature broken, no workaround
+   - Medium: Feature impaired, workaround exists
+   - Low: Minor issue, cosmetic
+
+   **Impact Assessment**
+   - Users affected: All / Subset / Single
+   - Business impact: Revenue / Reputation / Operations
+   - Frequency: Always / Often / Rarely
+
+   **Urgency Assessment**
+   - Blocking release?
+   - Customer escalation?
+   - Compliance issue?
+
+3. **Calculate Priority**
+   ```
+   Priority = Severity × Impact × Urgency
+   
+   P0 (Critical): Fix immediately, drop everything
+   P1 (High): Fix in current sprint
+   P2 (Medium): Fix in next sprint
+   P3 (Low): Backlog, fix when possible
+   ```
+
+4. **Generate Triage Report**
+   ```markdown
+   # Bug Triage Report
+   
+   **Date**: <date>
+   **Triaged By**: <name>
+   **Total Bugs**: <count>
+   
+   ## Summary
+   | Priority | Count | Action |
+   |----------|-------|--------|
+   | P0 | X | Immediate fix |
+   | P1 | Y | Current sprint |
+   | P2 | Z | Next sprint |
+   | P3 | W | Backlog |
+   
+   ## P0 - Critical (Fix Immediately)
+   | ID | Title | Severity | Impact | Assignee |
+   |----|-------|----------|--------|----------|
+   | #123 | ... | Critical | All users | @dev |
+   
+   ## P1 - High (Current Sprint)
+   | ID | Title | Severity | Impact | Assignee |
+   |----|-------|----------|--------|----------|
+   | #124 | ... | High | Subset | @dev |
+   
+   ## P2 - Medium (Next Sprint)
+   | ID | Title | Severity | Impact | Notes |
+   |----|-------|----------|--------|-------|
+   | #125 | ... | Medium | Low | Workaround exists |
+   
+   ## P3 - Low (Backlog)
+   | ID | Title | Notes |
+   |----|-------|-------|
+   | #126 | ... | Cosmetic issue |
+   
+   ## Recommendations
+   - <recommendation-1>
+   - <recommendation-2>
+   ```
+
+5. **Update Bug Statuses**
+   - Set priority labels
+   - Assign to appropriate team members
+   - Add to sprint if P0/P1
+
+## Output
+
+- Triage report
+- Updated bug priorities
+- Sprint recommendations
+
+$ARGUMENTS

package/templates/.claude/commands/qakit/bug/verify.md

@@ -0,0 +1,106 @@
+# Verify Bug Fix
+
+Verify that a bug fix resolves the issue without introducing regressions.
+
+## Usage
+
+```
+/qakit:bug/verify <bug-id-or-pr>
+```
+
+## Instructions
+
+Verify the bug fix thoroughly:
+
+1. **Review the Fix**
+   - Read the bug description
+   - Review the code changes
+   - Understand the fix approach
+
+2. **Verify Original Issue**
+   - Follow original reproduction steps
+   - Confirm bug no longer occurs
+   - Test on affected environments
+
+3. **Test Edge Cases**
+   - Test boundary conditions
+   - Test with different data
+   - Test related functionality
+
+4. **Check for Regressions**
+   - Run related test suites
+   - Test adjacent features
+   - Verify no new issues introduced
+
+5. **Generate Verification Report**
+   ```markdown
+   # Bug Fix Verification Report
+   
+   ## Bug Information
+   - **Bug ID**: <id>
+   - **Title**: <title>
+   - **Fix PR/Commit**: <reference>
+   - **Fixed By**: <developer>
+   
+   ## Verification Status
+   - [ ] Original issue resolved
+   - [ ] Edge cases tested
+   - [ ] No regressions found
+   - [ ] Tests added/updated
+   
+   ## Test Results
+   
+   ### Original Issue
+   | Test | Result | Notes |
+   |------|--------|-------|
+   | Reproduction steps | ✅ Pass | Bug no longer occurs |
+   
+   ### Edge Cases
+   | Test | Result | Notes |
+   |------|--------|-------|
+   | Empty input | ✅ Pass | Handled correctly |
+   | Large data | ✅ Pass | No issues |
+   | Concurrent access | ✅ Pass | Thread-safe |
+   
+   ### Regression Tests
+   | Test Suite | Result | Notes |
+   |------------|--------|-------|
+   | Unit tests | ✅ Pass | All passing |
+   | Integration tests | ✅ Pass | All passing |
+   | E2E tests | ✅ Pass | All passing |
+   
+   ## New Tests Added
+   - `test/unit/component.test.ts` - Tests for fix
+   - `test/e2e/feature.spec.ts` - Regression test
+   
+   ## Environments Tested
+   - [ ] Development
+   - [ ] Staging
+   - [ ] Production (if applicable)
+   
+   ## Verification Result
+   - [ ] **VERIFIED** - Fix is complete and working
+   - [ ] **FAILED** - Issue still exists or regression found
+   - [ ] **PARTIAL** - Fix works but needs additional changes
+   
+   ## Notes
+   <additional-observations>
+   
+   ## Recommendation
+   - [ ] Ready to merge/deploy
+   - [ ] Needs additional work
+   - [ ] Needs more testing
+   ```
+
+6. **Update Bug Status**
+   - Mark as verified if passing
+   - Reopen if issues found
+   - Add verification notes
+
+## Output
+
+- Verification report
+- Test results
+- Status update recommendation
+
+$ARGUMENTS

package/templates/.claude/commands/qakit/config/init-qa.md

@@ -0,0 +1,107 @@
+# Initialize QA Configuration
+
+Set up QA configuration for the project.
+
+## Usage
+
+```
+/qakit:config/init-qa [options]
+```
+
+## Instructions
+
+Initialize QA configuration for this project by:
+
+1. **Detect Project Type**
+   - Scan package.json, requirements.txt, or other config files
+   - Identify the tech stack (React, Node, Python, etc.)
+   - Detect existing test frameworks
+
+2. **Create QA Configuration File**
+   Create `.qakit.json` in project root with:
+   ```json
+   {
+     "version": "1.0.0",
+     "project": {
+       "name": "<project-name>",
+       "type": "<detected-type>"
+     },
+     "testing": {
+       "unit": {
+         "framework": "<detected-or-recommended>",
+         "directory": "tests/unit"
+       },
+       "integration": {
+         "framework": "<detected-or-recommended>",
+         "directory": "tests/integration"
+       },
+       "e2e": {
+         "framework": "playwright|webdriverio",
+         "directory": "tests/e2e"
+       },
+       "api": {
+         "framework": "<detected-or-recommended>",
+         "directory": "tests/api"
+       }
+     },
+     "coverage": {
+       "threshold": {
+         "statements": 80,
+         "branches": 80,
+         "functions": 80,
+         "lines": 80
+       }
+     },
+     "integrations": {
+       "jira": {
+         "enabled": false,
+         "projectKey": ""
+       },
+       "testmo": {
+         "enabled": false,
+         "projectId": ""
+       }
+     },
+     "reporting": {
+       "outputDir": "test-reports",
+       "formats": ["html", "json"]
+     }
+   }
+   ```
+
+3. **Set Up Directory Structure**
+   Create recommended test directories if they don't exist:
+   - `tests/unit/`
+   - `tests/integration/`
+   - `tests/e2e/`
+   - `tests/api/`
+   - `tests/fixtures/`
+   - `test-reports/`
+
+4. **Generate Test Templates**
+   Create starter test files based on detected framework
+
+5. **Update .gitignore**
+   Add test artifacts to .gitignore:
+   ```
+   test-reports/
+   coverage/
+   .qakit.local.json
+   ```
+
+## Options
+
+- `--force` - Overwrite existing configuration
+- `--minimal` - Create minimal configuration
+- `--with-jira` - Include Jira integration setup
+- `--with-testmo` - Include Testmo integration setup
+
+## Output
+
+After initialization:
+- `.qakit.json` - Main QA configuration
+- Test directory structure created
+- Starter test templates generated
+- Integration configs if requested
+
+$ARGUMENTS