pi-subagents 0.19.2 → 0.19.3
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 +5 -0
- package/package.json +1 -1
- package/prompts/parallel-review.md +4 -2
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,11 @@
|
|
|
2
2
|
|
|
3
3
|
## [Unreleased]
|
|
4
4
|
|
|
5
|
+
## [0.19.3] - 2026-04-27
|
|
6
|
+
|
|
7
|
+
### Changed
|
|
8
|
+
- Updated the packaged `/parallel-review` prompt so reviewer angles are generated dynamically from the user's intent, plan, implemented code, and current diff, with the listed angles framed as examples rather than fixed defaults.
|
|
9
|
+
|
|
5
10
|
## [0.19.2] - 2026-04-27
|
|
6
11
|
|
|
7
12
|
### Added
|
package/package.json
CHANGED
|
@@ -6,7 +6,9 @@ Launch parallel reviewers for an adversarial review of the current work.
|
|
|
6
6
|
|
|
7
7
|
Use fresh context, not forked context, unless I explicitly ask for forked context. Reviewers should inspect the repository, relevant instructions, and current diff directly from files and commands. Do not rely on the main conversation history.
|
|
8
8
|
|
|
9
|
-
Give each reviewer a distinct angle.
|
|
9
|
+
Give each reviewer a distinct angle. Generate the angles dynamically from the user's intent, the plan, the implemented code, and the current diff. If I specify angles, use mine. Otherwise, choose the highest-value review angles for this specific work.
|
|
10
|
+
|
|
11
|
+
These are examples, not fixed defaults:
|
|
10
12
|
|
|
11
13
|
1. Correctness and regressions
|
|
12
14
|
Check whether the change satisfies the request, preserves existing behavior, handles edge cases, and avoids hidden runtime failures.
|
|
@@ -17,7 +19,7 @@ Give each reviewer a distinct angle. Unless I specify angles, use these three:
|
|
|
17
19
|
3. Simplicity and maintainability
|
|
18
20
|
Check for unnecessary complexity, duplicate structure, single-use wrappers, brittle abstractions, confusing names, verbosity, and cleanup that is clearly worth doing.
|
|
19
21
|
|
|
20
|
-
|
|
22
|
+
Choose or adapt angles when the work calls for it:
|
|
21
23
|
- TypeScript-heavy changes: include type safety, source-of-truth types, casts, and error-boundary discipline.
|
|
22
24
|
- UI-heavy changes: include UX, accessibility, copy, and visual quality.
|
|
23
25
|
- Security-sensitive changes: include unsafe input/output handling, auth boundaries, privacy, and data exposure.
|