speccrew 0.5.13 → 0.5.15

package/.speccrew/skills/speccrew-test-reporter/SKILL.md

@@ -0,0 +1,297 @@
+---
+name: speccrew-test-reporter
+description: "SpecCrew Test Reporter. Generates comprehensive test reports and individual bug reports from test execution results. Performs root cause analysis and severity classification."
+tools: Read, Write, Glob, Grep
+---
+
+# Trigger Scenarios
+
+- When speccrew-test-runner completes and outputs execution results
+- When user explicitly requests "generate test report", "create bug reports"
+- When test execution results need to be converted to human-readable reports
+
+# Role Positioning
+
+**Primary Role**: Test Report Generator
+
+**Responsibilities**:
+- Read structured test execution results from speccrew-test-runner
+- Generate comprehensive test reports with statistics and analysis
+- Generate individual bug reports for each failed test case
+- Perform detailed root cause analysis with impact assessment
+- Classify bug severity for prioritization
+- Output human-readable documents for stakeholders
+
+**Upstream Dependencies**: speccrew-test-runner
+**Downstream Consumers**: speccrew-test-manager, development teams, QA teams
+
+# Workflow
+
+## Absolute Constraints
+
+> **These rules apply to ALL document generation steps. Violation = task failure.**
+
+1. **FORBIDDEN: `create_file` for documents** — NEVER use `create_file` to write test reports or bug reports. Documents MUST be created by copying the template then filling sections with `search_replace`.
+
+2. **FORBIDDEN: Full-file rewrite** — NEVER replace the entire document content in a single operation. Always use targeted `search_replace` on specific sections.
+
+3. **MANDATORY: Template-first workflow** — Copy template MUST execute before filling sections.
+
+4. **MUST: One Bug Per File** — Each failed test gets its own bug report file for independent tracking.
+
+5. **MUST: Severity Classification** — Always classify bug severity for prioritization.
+
+6. **MUST: Actionable Reports** — Bug reports must include suggested fix direction.
+
+## Input Parameters
+
+| Parameter | Required | Description |
+|-----------|----------|-------------|
+| `execution_results_path` | Yes | Path to test execution results from speccrew-test-runner |
+| `test_cases_path` | Yes | Path to test cases document with expected results |
+| `output_dir` | Yes | Directory for report output |
+| `feature_name` | Yes | Feature name for output file naming |
+| `platform_id` | Yes | Target platform identifier |
+
+## Step 1: Read Inputs
+
+Read the following documents in order:
+
+1. **Test Execution Results**: `execution_results_path`
+   - Structured execution data from speccrew-test-runner
+   - Contains test results, deviations, environment info
+
+2. **Test Cases Document**: `test_cases_path`
+   - Original test case definitions with expected results
+   - Used for detailed comparison and bug report generation
+
+**Input Validation**:
+- Verify execution results document exists and follows expected format
+- If input is missing or malformed, report to user and stop
+
+## Step 2: Analyze Execution Results
+
+### 2.1 Extract Summary Statistics
+
+Parse execution results to extract:
+- Total tests executed
+- Pass/fail/error/skip counts
+- Pass rate percentage
+- Execution duration
+- Platform and framework information
+
+### 2.2 Identify Failed Tests
+
+Extract all tests with status FAIL, ERROR, or SKIP:
+- TC ID for traceability
+- Test name and description
+- Error messages and stack traces
+- Expected vs actual results
+
+### 2.3 Classify by Test Dimension
+
+Group results by test dimension (if available):
+- Happy Path
+- Boundary Value
+- Exception Handling
+- Business Rules
+- Permission/Security
+- Data Validation
+
+## Step 3: Generate Test Report
+
+### 3.1 Read Template
+
+Read template: `templates/TEST-REPORT-TEMPLATE.md`
+
+### 3.2 Copy Template to Report Path
+
+1. **Read template** from Step 3.1
+2. **Replace top-level placeholders** (feature name, platform, execution date, etc.)
+3. **Create the document** using `create_file` at: `{output_dir}/reports/{feature}-test-report.md`
+4. **Verify**: Document has complete section structure
+
+### 3.3 Fill Each Section Using search_replace
+
+Fill each section with test execution data.
+
+> **CRITICAL CONSTRAINTS:**
+> - **FORBIDDEN: `create_file` to rewrite the entire document**
+> - **MUST use `search_replace` to fill each section individually**
+> - **All section titles MUST be preserved**
+
+**Section Filling Guide:**
+
+| Section | Content |
+|---------|---------|
+| **Execution Summary** | Feature name and platform, test framework and version, execution date and duration, overall pass rate |
+| **Results Overview** | Counts and percentages for all result types, visual pass/fail indication |
+| **Results by Test Dimension** | Breakdown by test type (happy path, boundary, exception, etc.), pass rate per dimension |
+| **Failed Test Details** | Table of all failed tests, links to corresponding bug reports |
+| **Coverage Status** | Requirement-to-test-case mapping, status per requirement |
+| **Environment Information** | OS, runtime, framework versions, key dependencies |
+| **Recommendations** | Priority fixes needed, suggested next steps |
+
+## Step 4: Generate Bug Reports
+
+### 4.1 Read Template
+
+Read template: `templates/BUG-REPORT-TEMPLATE.md`
+
+### 4.2 Create Bug Reports Directory
+
+Ensure directory exists: `{output_dir}/bugs/`
+
+### 4.3 Generate Bug Report for Each Failure
+
+For each FAIL or ERROR type failure:
+
+1. **Read template** from Step 4.1: `templates/BUG-REPORT-TEMPLATE.md`
+2. **Replace top-level placeholders** (Bug ID, feature name, TC ID)
+3. **Create document** using `create_file` at: `{output_dir}/bugs/{feature}-bug-{seq}.md`
+
+### 4.4 Fill Each Bug Report Using search_replace
+
+For each bug report created in 4.3, fill sections using `search_replace`:
+
+> **CRITICAL CONSTRAINTS:**
+> - **FORBIDDEN: `create_file` to rewrite the entire document**
+> - **MUST use `search_replace` to fill each section individually**
+
+**Section Filling Guide:**
+
+1. **Assign Bug ID**: `BUG-{feature}-{seq}` (sequential numbering)
+
+2. **Determine Severity**:
+   | Criteria | Severity |
+   |----------|----------|
+   | Blocks core functionality, no workaround | Critical |
+   | Major feature broken, workaround exists | High |
+   | Minor feature issue, cosmetic problem | Medium |
+   | Enhancement, minor improvement | Low |
+
+3. **Fill Bug Report Content**:
+   - Bug title reflecting the failure
+   - Related TC ID for traceability
+   - Clear reproduction steps
+   - Expected result from test case
+   - Actual result from execution
+   - Relevant error log excerpt
+   - Suggested fix direction
+
+### 4.4 Root Cause Analysis
+
+For each bug, perform detailed analysis:
+
+| Analysis Aspect | Description |
+|-----------------|-------------|
+| **Error Category** | Syntax, Logic, Integration, Environment, Performance |
+| **Impact Assessment** | What functionality is affected |
+| **Likely Cause** | Probable source of the issue |
+| **Suggested Fix** | Direction for resolution |
+
+### 4.5 Bug Report Quality Checklist
+
+Each bug report must include:
+- [ ] Unique Bug ID
+- [ ] Related TC ID
+- [ ] Severity classification
+- [ ] Clear reproduction steps
+- [ ] Expected vs actual result
+- [ ] Relevant log excerpt
+- [ ] Suggested fix direction
+- [ ] Root cause analysis
+
+## Step 5: Update Test Report with Bug Links
+
+After all bug reports are generated, update the test report:
+
+1. Read the test report: `{output_dir}/reports/{feature}-test-report.md`
+2. Update "Failed Test Details" section with links to bug reports
+3. Use `search_replace` to add bug report file paths
+
+## Output
+
+### Output Files
+
+| File | Path | Description |
+|------|------|-------------|
+| Test Report | `{output_dir}/reports/{feature}-test-report.md` | Comprehensive test execution report |
+| Bug Reports | `{output_dir}/bugs/{feature}-bug-{seq}.md` | Individual bug report per failure |
+
+### Output Structure
+
+```
+{output_dir}/
+├── reports/
+│   └── {feature}-test-report.md
+└── bugs/
+    ├── {feature}-bug-001.md
+    ├── {feature}-bug-002.md
+    └── ...
+```
+
+# Key Rules
+
+| Rule | Description |
+|------|-------------|
+| **Template-First Workflow** | Always copy template before filling sections |
+| **One Bug Per File** | Each bug gets its own report file for tracking |
+| **Severity Classification** | Always classify bug severity for prioritization |
+| **Actionable Reports** | Bug reports must include suggested fix direction |
+| **TC ID Traceability** | Every bug must be traced back to its TC ID |
+| **Root Cause Analysis** | Provide detailed analysis of failure causes |
+| **No Execution** | This skill does NOT execute tests, only generates reports |
+
+# Checklist
+
+- [ ] Execution results document loaded successfully
+- [ ] Test report generated with complete statistics
+- [ ] Results broken down by test dimension
+- [ ] Failed tests linked to corresponding bug reports
+- [ ] Each FAIL/ERROR has a corresponding bug report
+- [ ] Bug severity classified (Critical/High/Medium/Low)
+- [ ] Root cause analysis completed for each bug
+- [ ] All bug reports written to correct output path
+- [ ] Test report written to correct output path
+- [ ] Bug links updated in test report
+
+---
+
+# Task Completion Report
+
+Upon completion (success or failure), output the following report format:
+
+## Success Report
+```
+## Task Completion Report
+- **Status**: SUCCESS
+- **Task ID**: <from dispatch context, e.g., "test-reporter-web-vue">
+- **Platform**: <platform_id, e.g., "web-vue">
+- **Phase**: test_reporting
+- **Output Files**:
+  - `{output_dir}/reports/{feature}-test-report.md`
+  - `{output_dir}/bugs/{feature}-bug-{seq}.md` (if any failures)
+- **Summary**: Generated test report with {total} tests, {failed} bugs reported
+```
+
+## Failure Report
+```
+## Task Completion Report
+- **Status**: FAILED
+- **Task ID**: <from dispatch context>
+- **Platform**: <platform_id>
+- **Phase**: test_reporting
+- **Output Files**: <list of partial outputs or "None">
+- **Summary**: Test report generation failed during {step}
+- **Error**: <detailed error description>
+- **Error Category**: INPUT_MISSING | TEMPLATE_ERROR | WRITE_ERROR | BLOCKED
+- **Partial Outputs**: <list of files that were generated before failure, or "None">
+- **Recovery Hint**: <suggestion for recovery>
+```
+
+**Error Category Definitions**:
+- `INPUT_MISSING`: Required execution results or test cases document not available
+- `TEMPLATE_ERROR`: Template file missing or malformed
+- `WRITE_ERROR`: File system error during report generation
+- `BLOCKED`: Blocked by missing upstream dependency

package/.speccrew/skills/{speccrew-test-execute → speccrew-test-reporter}/templates/BUG-REPORT-TEMPLATE.md

@@ -1,6 +1,7 @@
 # Bug Report: {Bug Title}
 
 ## Bug Information
+
 | Item | Value |
 |------|-------|
 | Bug ID | BUG-{feature}-{seq} |
@@ -9,38 +10,60 @@
 | Status | Open |
 | Platform | {platform_id} |
 | Detected Date | {date} |
-| Detected By | speccrew-test-execute |
+| Detected By | speccrew-test-reporter |
 
 ## Description
+
 {brief_description_of_the_bug}
 
 ## Reproduction Steps
+
 1. {step_1}
 2. {step_2}
 3. {step_3}
 
 ## Expected Result
+
 {expected_result_from_test_case}
 
 ## Actual Result
+
 {actual_result_observed}
 
 ## Error Log
+
 ```
 {relevant_error_log_or_stack_trace}
 ```
 
 ## Environment
+
 | Item | Value |
 |------|-------|
 | OS | {os} |
 | Runtime | {runtime_version} |
 | Related Module | {module_name} |
 
+## Root Cause Analysis
+
+### Error Category
+
+{syntax_logic_integration_environment_performance}
+
+### Impact Assessment
+
+{what_functionality_is_affected}
+
+### Likely Cause
+
+{probable_source_of_the_issue}
+
 ## Suggested Fix Direction
+
 {analysis_of_likely_root_cause_and_suggested_fix_approach}
 
 ## Related Files
+
 - Test File: {test_file_path}
 - Source File: {likely_source_file} (if identifiable)
 

package/.speccrew/skills/{speccrew-test-execute → speccrew-test-reporter}/templates/TEST-REPORT-TEMPLATE.md

@@ -1,6 +1,7 @@
 # Test Execution Report: {Feature Name}
 
 ## 1. Execution Summary
+
 | Item | Value |
 |------|-------|
 | Feature Name | {feature_name} |
@@ -8,9 +9,10 @@
 | Test Framework | {framework} |
 | Execution Date | {date} |
 | Total Duration | {duration} |
-| Executor | speccrew-test-execute |
+| Executor | speccrew-test-reporter |
 
 ## 2. Results Overview
+
 | Metric | Count | Percentage |
 |--------|-------|------------|
 | Total | {total} | 100% |
@@ -20,6 +22,7 @@
 | Skipped | {skipped} | {skip_rate}% |
 
 ## 3. Results by Test Dimension
+
 | Dimension | Total | Passed | Failed | Pass Rate |
 |-----------|-------|--------|--------|-----------|
 | Happy Path | {n} | {n} | {n} | {rate}% |
@@ -30,16 +33,19 @@
 | Data Validation | {n} | {n} | {n} | {rate}% |
 
 ## 4. Failed Test Details
+
 | TC ID | Test Name | Failure Type | Error Message | Bug Report |
 |-------|-----------|-------------|---------------|------------|
 | {tc_id} | {test_name} | FAIL/ERROR | {message} | {bug_report_link} |
 
 ## 5. Coverage Status
+
 | Requirement ID | Test Case IDs | Status |
 |---------------|---------------|--------|
 | {req_id} | {tc_ids} | Pass/Fail/Partial |
 
 ## 6. Environment Information
+
 | Item | Value |
 |------|-------|
 | OS | {os} |
@@ -48,6 +54,7 @@
 | Dependencies | {key_dependencies} |
 
 ## 7. Recommendations
+
 - {recommendation_1}
 - {recommendation_2}