@sylphx/flow 1.4.6 → 1.4.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +28 -0
- package/assets/agents/coder.md +91 -98
- package/assets/agents/orchestrator.md +73 -339
- package/assets/agents/reviewer.md +68 -101
- package/assets/agents/writer.md +80 -272
- package/assets/output-styles/silent.md +8 -4
- package/assets/rules/code-standards.md +78 -137
- package/assets/rules/core.md +57 -25
- package/assets/rules/workspace.md +485 -0
- package/assets/slash-commands/cleanup.md +60 -0
- package/assets/slash-commands/improve.md +154 -0
- package/assets/slash-commands/polish.md +88 -0
- package/assets/slash-commands/quality.md +182 -0
- package/assets/slash-commands/release.md +104 -0
- package/package.json +2 -2
- package/src/commands/init-core.ts +0 -10
- package/src/core/installers/file-installer.ts +0 -27
- package/src/utils/sync-utils.ts +3 -16
- package/assets/slash-commands/commit.md +0 -23
- package/assets/slash-commands/context.md +0 -112
- package/assets/slash-commands/explain.md +0 -35
- package/assets/slash-commands/review.md +0 -39
- package/assets/slash-commands/test.md +0 -30
|
@@ -1,30 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
description: Write comprehensive tests for code
|
|
3
|
-
---
|
|
4
|
-
|
|
5
|
-
# Write Tests
|
|
6
|
-
|
|
7
|
-
## Context
|
|
8
|
-
|
|
9
|
-
$ARGUMENTS
|
|
10
|
-
|
|
11
|
-
## Your Task
|
|
12
|
-
|
|
13
|
-
Write comprehensive tests for the code above (or at the specified location) that include:
|
|
14
|
-
|
|
15
|
-
1. **Unit Tests**
|
|
16
|
-
- Test individual functions/methods
|
|
17
|
-
- Cover edge cases and boundary conditions
|
|
18
|
-
- Test error handling
|
|
19
|
-
|
|
20
|
-
2. **Integration Tests** (if applicable)
|
|
21
|
-
- Test component interactions
|
|
22
|
-
- Test with realistic data
|
|
23
|
-
|
|
24
|
-
3. **Test Coverage**
|
|
25
|
-
- Aim for high coverage of critical paths
|
|
26
|
-
- Include positive and negative test cases
|
|
27
|
-
- Test validation and error conditions
|
|
28
|
-
|
|
29
|
-
Use the project's existing testing framework and follow its conventions.
|
|
30
|
-
Ensure tests are readable, maintainable, and properly documented.
|