diff options
| author | Arpit Chakladar <arpit@chakladar.me> | 2026-09-29 23:45:25 +0530 |
|---|---|---|
| committer | Arpit Chakladar <arpit@chakladar.me> | 2026-09-29 23:45:25 +0530 |
| commit | 33519df0fff478526d217d04190577b33c5bf7d0 (patch) | |
| tree | 18f6ee9bb8101381212038d16099e59d250b7080 /modules/development/pi-coding-agent/skills/testing/SKILL.md | |
| parent | 7975de6d03289bcc143137d5458486def5adc672 (diff) | |
| parent | 871a29efd370088f669c4f2b9e20b8992406a444 (diff) | |
| download | home-manager-config-33519df0fff478526d217d04190577b33c5bf7d0.tar.gz home-manager-config-33519df0fff478526d217d04190577b33c5bf7d0.zip | |
Merge branch 'adding-pi-harness'
Diffstat (limited to 'modules/development/pi-coding-agent/skills/testing/SKILL.md')
| -rw-r--r-- | modules/development/pi-coding-agent/skills/testing/SKILL.md | 42 |
1 files changed, 42 insertions, 0 deletions
diff --git a/modules/development/pi-coding-agent/skills/testing/SKILL.md b/modules/development/pi-coding-agent/skills/testing/SKILL.md new file mode 100644 index 0000000..4785fe7 --- /dev/null +++ b/modules/development/pi-coding-agent/skills/testing/SKILL.md @@ -0,0 +1,42 @@ +--- +name: testing +description: "Figure out the project's existing test strategy, add targeted tests, run the smallest useful test set, then broaden validation." +--- + +# Testing Skill + +Figure out the project's existing test strategy, add targeted tests, run the smallest useful test set, then broaden validation. + +## Subagents +When you need to delegate sub‑tasks, use the `pi-subagents` skill. + +**Example:** To expand test coverage, assign a **scout** to run the existing unit test suite and report gaps, another **scout** to generate property-based tests for the `parser` module, and an **implementer** to add integration tests for the `api` endpoints while a **reviewer** verifies the new tests pass. + +*You may adapt the delegation pattern to fit the exact requirements of the codebase.* + +## Process + +### 1. Discover +- Find test framework and conventions +- Locate existing test files +- Understand test organization + +### 2. Target +- Write tests for the specific change +- Focus on behavior, not implementation +- Cover edge cases and error paths + +### 3. Run Small +- Execute only affected tests first +- Use test filtering if available +- Verify new tests pass + +### 4. Broaden +- Run full test suite +- Check for flaky tests +- Validate integration points + +### 5. Report +- Document what was tested +- Note any skipped tests +- Report coverage gaps |
