ai-qakit 1.0.0

package/templates/.claude/commands/qakit/feature/update.md

@@ -0,0 +1,136 @@
+# Update Feature Specification
+
+Update an existing feature specification with new information.
+
+## Usage
+
+```
+/qakit:feature/update <feature-file> [options]
+```
+
+## Examples
+
+```
+# Update from Jira (sync latest changes)
+/qakit:feature/update docs/features/AUTH-001.md --from-jira
+
+# Add new user story
+/qakit:feature/update docs/features/AUTH-001.md --add-story "Password reset via SMS"
+
+# Update status
+/qakit:feature/update docs/features/AUTH-001.md --status "In Testing"
+
+# Sync test cases (update test case table)
+/qakit:feature/update docs/features/AUTH-001.md --sync-tests
+```
+
+## Options
+
+| Option | Description |
+|--------|-------------|
+| `--from-jira` | Sync latest data from linked Jira tickets |
+| `--add-story` | Add a new user story |
+| `--status` | Update feature status |
+| `--sync-tests` | Update test cases table from generated tests |
+| `--add-ac` | Add acceptance criteria to a story |
+
+## Instructions
+
+### 1. Read Existing Feature File
+
+- Parse current feature spec
+- Identify linked Jira tickets
+- Get current user stories and ACs
+
+### 2. Apply Updates
+
+**For `--from-jira`:**
+- Fetch latest from Jira MCP (or prompt for paste)
+- Compare with existing content
+- Highlight changes for review
+- Update fields that changed
+
+**For `--add-story`:**
+- Generate new US-XXX ID (increment from last)
+- Create user story structure
+- Prompt for acceptance criteria
+
+**For `--sync-tests`:**
+- Scan `tests/test-cases/` for related test cases
+- Update "Test Cases" table with actual status
+- Link test case files
+
+### 3. Update Change History
+
+Add entry to Change History table:
+
+```markdown
+| Date | Author | Changes |
+|------|--------|---------|
+| 2024-01-20 | AI | Synced from Jira, added US-003 |
+```
+
+### 4. Save Updated File
+
+- Preserve existing content structure
+- Only modify changed sections
+- Update "Last Updated" date
+
+## Sync from Jira Example
+
+**Before:**
+```markdown
+### US-001: Login with Email
+
+| Field | Value |
+|-------|-------|
+| **Jira** | [PROJ-101](https://jira.company.com/browse/PROJ-101) |
+| **Priority** | P1 |
+| **Sprint** | Sprint 15 |
+```
+
+**After sync (priority changed in Jira):**
+```markdown
+### US-001: Login with Email
+
+| Field | Value |
+|-------|-------|
+| **Jira** | [PROJ-101](https://jira.company.com/browse/PROJ-101) |
+| **Priority** | P0 | ← Updated
+| **Sprint** | Sprint 16 | ← Updated
+```
+
+## Test Cases Sync Example
+
+**Before:**
+```markdown
+## Test Cases (Generated)
+
+| Test Case ID | Title | Priority | Status |
+|--------------|-------|----------|--------|
+| WEB-LOGIN-001 | Verify login with valid credentials | P0 | Not Created |
+```
+
+**After `--sync-tests`:**
+```markdown
+## Test Cases (Generated)
+
+| Test Case ID | Title | Priority | Status |
+|--------------|-------|----------|--------|
+| WEB-LOGIN-001 | Verify login with valid credentials | P0 | ✅ Created |
+| WEB-LOGIN-002 | Validate invalid email error | P0 | ✅ Created |
+| WEB-LOGIN-003 | Verify account lockout | P1 | Not Created |
+```
+
+## Quality Checklist
+
+After update:
+
+- [ ] All changes are tracked in Change History
+- [ ] Jira links are still valid
+- [ ] New ACs have proper IDs (sequential)
+- [ ] Test cases table is accurate
+- [ ] Last Updated date is current
+
+$ARGUMENTS
+

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

@@ -0,0 +1,98 @@
+# QA Help Command
+
+Display available QA commands and their descriptions.
+
+## Usage
+
+```
+/qakit:help [category]
+```
+
+## Categories
+
+- `test` - Test creation and generation commands
+- `bug` - Bug investigation and reporting commands
+- `review` - Test review and coverage commands
+- `metrics` - Quality metrics and dashboards
+- `spec` - Spec-driven QA workflow commands
+- `regression` - Regression testing commands
+- `api` - API testing commands
+- `e2e` - End-to-end testing commands
+- `perf` - Performance testing commands
+- `a11y` - Accessibility testing commands
+- `jira` - Jira integration commands
+- `testmo` - Testmo integration commands
+
+## Available Commands
+
+### Core Commands
+- `/qakit:help` - Show this help
+- `/qakit:ask` - Ask QA-related questions
+- `/qakit:config/init-qa` - Initialize QA configuration
+
+### Test Commands
+- `/qakit:test/create-test-case` - Create a test case
+- `/qakit:test/create-test-suite` - Create a test suite
+- `/qakit:test/generate-api-tests` - Generate API tests
+- `/qakit:test/generate-ui-tests` - Generate UI tests
+- `/qakit:test/generate-e2e` - Generate E2E tests
+- `/qakit:test/generate-data` - Generate test data
+
+### Bug Commands
+- `/qakit:bug/investigate` - Investigate a bug
+- `/qakit:bug/report` - Create bug report
+- `/qakit:bug/reproduce` - Create reproduction steps
+- `/qakit:bug/triage` - Triage bugs
+- `/qakit:bug/verify` - Verify bug fix
+
+### Review Commands
+- `/qakit:review/test-review` - Review test quality
+- `/qakit:review/coverage` - Analyze test coverage
+- `/qakit:review/quality-gate` - Check quality gates
+
+### Metrics Commands
+- `/qakit:metrics/coverage` - Coverage metrics
+- `/qakit:metrics/dashboard` - Quality dashboard
+- `/qakit:metrics/trends` - Quality trends
+
+### Spec Workflow Commands
+- `/qakit:spec/task` - Create QA task from spec
+- `/qakit:spec/analyze` - Analyze requirements for testing
+- `/qakit:spec/plan` - Create test plan from spec
+- `/qakit:spec/execute` - Execute test plan
+- `/qakit:spec/report` - Generate test report
+- `/qakit:spec/cook` - Full spec-to-test workflow
+
+### Regression Commands
+- `/qakit:regression/analyze` - Analyze regression impact
+- `/qakit:regression/select` - Select regression tests
+- `/qakit:regression/run` - Run regression suite
+- `/qakit:regression/report` - Regression report
+
+### API Testing Commands
+- `/qakit:api/analyze` - Analyze API for testing
+- `/qakit:api/generate` - Generate API tests
+- `/qakit:api/run` - Run API tests
+- `/qakit:api/contract` - Contract testing
+
+### E2E Testing Commands
+- `/qakit:e2e/scenario` - Create E2E scenario
+- `/qakit:e2e/page-object` - Generate page objects
+- `/qakit:e2e/generate` - Generate E2E tests
+- `/qakit:e2e/run` - Run E2E tests
+
+### Performance Testing Commands
+- `/qakit:perf/plan` - Create performance test plan
+- `/qakit:perf/script` - Generate performance scripts
+- `/qakit:perf/run` - Run performance tests
+- `/qakit:perf/analyze` - Analyze performance results
+
+### Accessibility Commands
+- `/qakit:a11y/audit` - Run accessibility audit
+- `/qakit:a11y/fix` - Fix accessibility issues
+
+### Integration Commands
+- `/qakit:jira/analyze` - Analyze Jira tickets for testing
+- `/qakit:jira/create-tests` - Create tests from Jira
+- `/qakit:testmo/sync` - Sync with Testmo
+- `/qakit:testmo/report` - Generate Testmo report

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

@@ -0,0 +1,329 @@
+# Analyze Jira Ticket for Testing
+
+Comprehensive analysis of Jira ticket including subtasks, linked issues, and comments to identify all testing needs.
+
+## Usage
+
+```
+/qakit:jira/analyze PROJ-123
+/qakit:jira/analyze https://yourcompany.atlassian.net/browse/PROJ-123
+```
+
+## Prerequisites
+
+Set environment variables:
+```bash
+export JIRA_BASE_URL="https://yourcompany.atlassian.net"
+export JIRA_EMAIL="your.email@company.com"
+export JIRA_API_TOKEN="your-api-token"
+```
+
+## Instructions
+
+### Step 1: Parse Input
+
+Extract ticket ID from input:
+- Direct ID: `PROJ-123`
+- URL: `https://company.atlassian.net/browse/PROJ-123` → extract `PROJ-123`
+
+### Step 2: Fetch Main Ticket
+
+```bash
+curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
+  "$JIRA_BASE_URL/rest/api/3/issue/{TICKET_ID}?expand=changelog"
+```
+
+Extract from response:
+- `.key` - Ticket ID
+- `.fields.summary` - Summary
+- `.fields.description` - Description (ADF)
+- `.fields.issuetype.name` - Type (Epic/Story/Bug/Task)
+- `.fields.status.name` - Status
+- `.fields.priority.name` - Priority
+- `.fields.labels` - Labels
+- `.fields.components` - Components
+- `.fields.assignee.displayName` - Assignee
+- `.fields.reporter.displayName` - Reporter
+- `.fields.subtasks` - Subtask list
+- `.fields.issuelinks` - Linked issues
+- `.fields.comment.comments` - Comments
+- `.fields.attachment` - Attachments
+- `.fields.customfield_10204` - Acceptance Criteria (may vary)
+
+### Step 3: Fetch Subtasks (Recursive)
+
+For each subtask in `.fields.subtasks`:
+```bash
+curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
+  "$JIRA_BASE_URL/rest/api/3/issue/{SUBTASK_KEY}"
+```
+
+Collect:
+- Subtask summary
+- Subtask status
+- Subtask acceptance criteria
+
+### Step 4: Fetch Linked Issues
+
+For each link in `.fields.issuelinks`:
+- Check `outwardIssue` or `inwardIssue`
+- Note link type: "blocks", "is blocked by", "relates to", "duplicates"
+
+```bash
+curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
+  "$JIRA_BASE_URL/rest/api/3/issue/{LINKED_KEY}"
+```
+
+Collect:
+- Linked issue summary
+- Link relationship
+- Linked issue status
+
+### Step 4.5: Fetch Confluence Links (If configured)
+
+**Get Remote Links (includes Confluence):**
+```bash
+curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
+  "$JIRA_BASE_URL/rest/api/3/issue/{TICKET_ID}/remotelink"
+```
+
+**Search Confluence for ticket mentions:**
+```bash
+curl -s -u "$CONFLUENCE_EMAIL:$CONFLUENCE_API_TOKEN" \
+  "$CONFLUENCE_BASE_URL/wiki/rest/api/content/search?cql=text~\"{TICKET_ID}\""
+```
+
+**Extract Confluence URLs from description/comments:**
+Look for patterns:
+- `https://company.atlassian.net/wiki/spaces/...`
+- `https://company.atlassian.net/wiki/pages/...`
+
+For each Confluence page found, fetch content:
+```bash
+curl -s -u "$CONFLUENCE_EMAIL:$CONFLUENCE_API_TOKEN" \
+  "$CONFLUENCE_BASE_URL/wiki/api/v2/pages/{PAGE_ID}?body-format=storage"
+```
+
+Extract from Confluence:
+- Page title
+- Requirements/specs
+- Test cases (if documented)
+- Related Jira tickets mentioned
+
+### Step 5: Analyze Comments
+
+Parse `.fields.comment.comments[]`:
+- Extract text from `.body` (ADF format)
+- Look for test-related keywords:
+  - "test", "testing", "QA", "verify", "check"
+  - "bug", "issue", "problem", "error"
+  - "passed", "failed", "blocked"
+  - "edge case", "scenario", "regression"
+- Extract mentioned users for context
+- Note any linked tickets in comments (inlineCard)
+
+### Step 6: Extract Test Requirements
+
+From all collected data, identify:
+
+1. **Acceptance Criteria** (from description or custom field)
+2. **Test Hints from Comments** (QA discussions, edge cases mentioned)
+3. **Related Functionality** (from linked issues)
+4. **Scope from Subtasks** (breakdown of work)
+5. **Risk Areas** (from bug links, blockers)
+
+### Step 7: Generate Analysis Report
+
+## Output Format
+
+```markdown
+# Jira Analysis: {TICKET_ID}
+
+## Ticket Overview
+
+| Field | Value |
+|-------|-------|
+| **Key** | PROJ-123 |
+| **Summary** | User authentication feature |
+| **Type** | Story |
+| **Status** | In Progress |
+| **Priority** | High |
+| **Assignee** | John Doe |
+| **Reporter** | Jane Smith |
+| **Labels** | auth, security, sprint-15 |
+| **Components** | Frontend, Backend |
+
+## Description
+
+{Parsed description text}
+
+## Acceptance Criteria
+
+| ID | Criteria | Type | Testable |
+|----|----------|------|----------|
+| AC-001 | WHEN valid credentials THEN login success | Functional | ✅ |
+| AC-002 | WHEN invalid email THEN show error | Validation | ✅ |
+| AC-003 | WHEN 5 failed attempts THEN lock account | Security | ✅ |
+
+## Subtasks ({count})
+
+| Key | Summary | Status | Test Impact |
+|-----|---------|--------|-------------|
+| PROJ-124 | Implement login form | Done | UI tests needed |
+| PROJ-125 | Add password validation | In Progress | Unit tests needed |
+| PROJ-126 | Integrate with auth service | To Do | Integration tests |
+
+## Linked Issues ({count})
+
+| Relationship | Key | Summary | Status | Test Impact |
+|--------------|-----|---------|--------|-------------|
+| blocks | PROJ-200 | Dashboard feature | Blocked | Dependency |
+| relates to | PROJ-150 | Password reset | Done | Related flow |
+| is blocked by | PROJ-100 | Auth service setup | Done | Prerequisite |
+
+## Comments Analysis
+
+### Test-Related Discussions
+
+| Date | Author | Key Points |
+|------|--------|------------|
+| 2024-01-15 | QA Lead | "Need to test edge case: special characters in password" |
+| 2024-01-16 | Dev | "Fixed bug with empty email validation" |
+| 2024-01-17 | PM | "Add test for remember me checkbox" |
+
+### Mentioned Edge Cases
+- Special characters in password
+- Empty email validation
+- Remember me functionality
+
+### Linked Tickets in Comments
+- PROJ-456 (bug fix related)
+- PROJ-789 (design doc)
+
+## Confluence Documentation ({count})
+
+### Linked Pages
+
+| Title | Space | Type | Relevance |
+|-------|-------|------|-----------|
+| [PRD - User Authentication](link) | PROJ | Requirements | Primary spec |
+| [Test Plan - Auth Feature](link) | QA | Test Plan | Test documentation |
+| [API Design - Auth Service](link) | TECH | Design | Technical reference |
+
+### Requirements from Confluence
+
+| Source | Requirement |
+|--------|-------------|
+| PRD - User Auth | User must login with email/password |
+| PRD - User Auth | Password minimum 8 characters |
+| PRD - User Auth | Session timeout after 30 minutes |
+
+### Existing Test Cases from Confluence
+
+| ID | Test Case | Source Page |
+|----|-----------|-------------|
+| TC-001 | Valid login flow | Test Plan - Auth |
+| TC-002 | Invalid credentials | Test Plan - Auth |
+| TC-003 | Password reset | Test Plan - Auth |
+
+### Additional Context from Docs
+- Architecture diagram in "API Design - Auth Service"
+- User flow mockups in "PRD - User Authentication"
+- Security requirements in "Security Guidelines"
+
+## Attachments ({count})
+
+| Filename | Type | Relevance |
+|----------|------|-----------|
+| mockup.png | Image | UI reference |
+| api-spec.pdf | Document | API contract |
+| test-data.xlsx | Spreadsheet | Test data |
+
+## Test Scenarios
+
+### Functional Tests
+| ID | Scenario | Priority | Source |
+|----|----------|----------|--------|
+| TS-001 | Valid login with email/password | P0 | AC-001 |
+| TS-002 | Invalid email format validation | P1 | AC-002 |
+| TS-003 | Account lockout after 5 attempts | P0 | AC-003 |
+| TS-004 | Special characters in password | P1 | Comment |
+| TS-005 | Remember me checkbox | P2 | Comment |
+
+### Integration Tests
+| ID | Scenario | Priority | Source |
+|----|----------|----------|--------|
+| IT-001 | Auth service integration | P0 | Subtask PROJ-126 |
+| IT-002 | Dashboard access after login | P1 | Linked PROJ-200 |
+
+### Edge Cases
+| ID | Scenario | Priority | Source |
+|----|----------|----------|--------|
+| EC-001 | Empty email submission | P1 | Comment |
+| EC-002 | SQL injection in login | P0 | Security |
+| EC-003 | Session timeout handling | P2 | Related PROJ-150 |
+
+## Risk Assessment
+
+| Risk | Level | Mitigation |
+|------|-------|------------|
+| Auth service dependency | High | Wait for PROJ-100 |
+| Security vulnerabilities | High | Security testing required |
+| UI consistency | Medium | Cross-browser testing |
+
+## Test Effort Estimation
+
+| Category | Count | Estimated Hours |
+|----------|-------|-----------------|
+| Functional Tests | 5 | 4h |
+| Integration Tests | 2 | 3h |
+| Edge Cases | 3 | 2h |
+| Security Tests | 2 | 2h |
+| **Total** | **12** | **11h** |
+
+## Recommendations
+
+1. **High Priority**: Complete security testing before release
+2. **Dependency**: Wait for PROJ-100 before integration tests
+3. **Coverage**: Add tests for edge cases mentioned in comments
+4. **Automation**: Automate login flow for regression
+
+## Next Steps
+
+1. Create test cases:
+   ```
+   /qakit:jira/create-tests PROJ-123
+   ```
+
+2. Generate feature spec:
+   ```
+   /qakit:feature/from-jira PROJ-123
+   ```
+
+3. Create test plan:
+   ```
+   /qakit:spec/plan docs/features/PROJ-123.md
+   ```
+```
+
+## Comment Keywords to Watch
+
+| Category | Keywords |
+|----------|----------|
+| Test hints | test, testing, QA, verify, check, validate |
+| Issues | bug, issue, problem, error, fail, broken |
+| Edge cases | edge case, corner case, scenario, what if |
+| Status | passed, failed, blocked, fixed, resolved |
+| Priority | critical, urgent, important, blocker |
+
+## Link Type Interpretation
+
+| Link Type | Test Impact |
+|-----------|-------------|
+| blocks / is blocked by | Dependency - test order matters |
+| relates to | Related functionality - consider together |
+| duplicates | Skip duplicate testing |
+| is cloned by | Similar tests may apply |
+| causes / is caused by | Root cause analysis |
+
+$ARGUMENTS