@jakkrichm/create-nexus-devflow 2.0.0 → 2.0.2

package/template/.claude/skills/test/SKILL.md

@@ -3,80 +3,80 @@ name: test
 description: Test workflow
 ---
 
----
-description: Test Generation and Execution - Generates missing tests, runs existing test suites, or checks test coverage for the project.
----
-# ๐Ÿงช Test Generation and Execution
-
-## Usage: `/13-Test [target]`
-
-Generates missing tests, runs existing test suites, or checks test coverage for the project.
-
-Primary behavior now lives in:
-
-```text
-.agents/skills/test-execution-and-coverage/SKILL.md
-```
-
-Treat this workflow file as a compatibility wrapper around that skill.
-
----
-
-## ๐Ÿ› ๏ธ Sub-commands
-
-- `/13-Test`                - Run all tests
-- `/13-Test [file/feature]` - Generate tests for a specific target
-- `/13-Test coverage`       - Show test coverage report
-- `/13-Test watch`          - Run tests in watch mode
-
----
-
-## ๐Ÿšฆ Internal Process
-
-### Scenario A: Generate Tests
-If the user requests tests for a target:
-1. **Analyze**: Identify functions, edge cases, and external dependencies.
-2. **Template Verification**: **MANDATORY:** Before generating the test plan, inspect `.agent/resources/schemas/test_report.template.md`, preserve its required layout, and replace placeholder text with concrete coverage, command output, failures, and gaps.
-3. **Generate Cases**: Develop Happy path, Error cases, Edge cases.
-4. **Write**: Implement the tests using the project's testing framework (Pytest, Jest, Vitest, etc.). Follow the `Arrange-Act-Assert` pattern and mock external dependencies.
-5. **Save Test Report**: Save the test plan and results to `devflow/reports/{date}-test-report-{target}.md` (where `{date}` is today's date in `YYYY-MM-DD` format and `{target}` is a slugified version of the file or feature name).
-
-### Scenario B: Execute Tests
-Use the project's native command (e.g., `npm test`, `pytest`) to run the tests and format the output clearly for the user. Highlight any failed tests with expected vs received values. Save the execution summary report matching the template to `devflow/reports/{date}-test-report-run.md` (where `{date}` is today's date in `YYYY-MM-DD` format).
-
----
-
-## ๐Ÿ›ก๏ธ Key Principles
-- **Test behavior, not implementation.**
-- **One assertion per test** (when practical).
-- **Descriptive test names.**
-- **Arrange-Act-Assert pattern.**
-- **Save Report**: Always save the test plan or results to disk for persistent logging.
-
-## ๐Ÿ“ Output Formats
-
-### For Test Generation
-Generate a summary indicating:
-- **Test Plan**: Table of Test Case, Type, Coverage (Happy path, error case, validation)
-- **Generated Tests**: File path and the code block
-- **Report Location**: Confirm the report has been written to the specified workspace path.
-- **Run command**: e.g. `npm test`
-
-### For Test Execution
-Display an organized output listing Passed/Failed files, and explicitly show the expectation vs received outcome for failed assertions.
-
-## Relationship To DevFlow 2.0
-
-- Classification: Companion command
-- Mainline status: Verification support command, not a numbered stage
-- Typical entry points: `/40-Implement`, `/50-Verify`, `Debug`
-- Typical handoff targets: `/50-Verify`, `Debug`, `QA-Orchestrate`
-
-## Sources
-
-- `AGENTS.md`
-- `.agents/skills/test-execution-and-coverage/SKILL.md`
-- `.agent/resources/schemas/test_report.template.md`
-- Related commands: `/40-Implement`, `/50-Verify`, `Debug`, `QA-Orchestrate`
-
-
+---
+description: Test Generation and Execution - Generates missing tests, runs existing test suites, or checks test coverage for the project.
+---
+# ๐Ÿงช Test Generation and Execution
+
+## Usage: `/13-Test [target]`
+
+Generates missing tests, runs existing test suites, or checks test coverage for the project.
+
+Primary behavior now lives in:
+
+```text
+.agents/skills/test-execution-and-coverage/SKILL.md
+```
+
+Treat this workflow file as a compatibility wrapper around that skill.
+
+---
+
+## ๐Ÿ› ๏ธ Sub-commands
+
+- `/13-Test`                - Run all tests
+- `/13-Test [file/feature]` - Generate tests for a specific target
+- `/13-Test coverage`       - Show test coverage report
+- `/13-Test watch`          - Run tests in watch mode
+
+---
+
+## ๐Ÿšฆ Internal Process
+
+### Scenario A: Generate Tests
+If the user requests tests for a target:
+1. **Analyze**: Identify functions, edge cases, and external dependencies.
+2. **Template Verification**: **MANDATORY:** Before generating the test plan, inspect `.agent/resources/schemas/test_report.template.md`, preserve its required layout, and replace placeholder text with concrete coverage, command output, failures, and gaps.
+3. **Generate Cases**: Develop Happy path, Error cases, Edge cases.
+4. **Write**: Implement the tests using the project's testing framework (Pytest, Jest, Vitest, etc.). Follow the `Arrange-Act-Assert` pattern and mock external dependencies.
+5. **Save Test Report**: Save the test plan and results to `devflow/reports/{date}-test-report-{target}.md` (where `{date}` is today's date in `YYYY-MM-DD` format and `{target}` is a slugified version of the file or feature name).
+
+### Scenario B: Execute Tests
+Use the project's native command (e.g., `npm test`, `pytest`) to run the tests and format the output clearly for the user. Highlight any failed tests with expected vs received values. Save the execution summary report matching the template to `devflow/reports/{date}-test-report-run.md` (where `{date}` is today's date in `YYYY-MM-DD` format).
+
+---
+
+## ๐Ÿ›ก๏ธ Key Principles
+- **Test behavior, not implementation.**
+- **One assertion per test** (when practical).
+- **Descriptive test names.**
+- **Arrange-Act-Assert pattern.**
+- **Save Report**: Always save the test plan or results to disk for persistent logging.
+
+## ๐Ÿ“ Output Formats
+
+### For Test Generation
+Generate a summary indicating:
+- **Test Plan**: Table of Test Case, Type, Coverage (Happy path, error case, validation)
+- **Generated Tests**: File path and the code block
+- **Report Location**: Confirm the report has been written to the specified workspace path.
+- **Run command**: e.g. `npm test`
+
+### For Test Execution
+Display an organized output listing Passed/Failed files, and explicitly show the expectation vs received outcome for failed assertions.
+
+## Relationship To DevFlow 2.0
+
+- Classification: Companion command
+- Mainline status: Verification support command, not a numbered stage
+- Typical entry points: `/40-Implement`, `/50-Verify`, `Debug`
+- Typical handoff targets: `/50-Verify`, `Debug`, `QA-Orchestrate`
+
+## Sources
+
+- `AGENTS.md`
+- `.agents/skills/test-execution-and-coverage/SKILL.md`
+- `.agent/resources/schemas/test_report.template.md`
+- Related commands: `/40-Implement`, `/50-Verify`, `Debug`, `QA-Orchestrate`
+
+