pi-review 1.1.2 → 1.1.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.
Files changed (4) hide show
  1. package/dist/index.d.ts.map +1 -1
  2. package/dist/index.js +3 -0
  3. package/package.json +1 -1
  4. package/src/index.ts +3 -0
package/dist/index.d.ts.map CHANGED
@@ -1 +1 @@
1
- {"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,YAAY,EAAgB,MAAM,iCAAiC,CAAC;AAsGlF,MAAM,CAAC,OAAO,UAAU,eAAe,CAAC,EAAE,EAAE,YAAY,QAmFvD"}
1
+ {"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,YAAY,EAAgB,MAAM,iCAAiC,CAAC;AAyGlF,MAAM,CAAC,OAAO,UAAU,eAAe,CAAC,EAAE,EAAE,YAAY,QAmFvD"}
package/dist/index.js CHANGED
@@ -14,6 +14,9 @@ Delegate tightly scoped repo-local research on relevant pre-existing subsystems,
14
14
  2. Focused review:
15
15
  Delegate one or more scoped reviews using the review surface, relevant reconnaissance note paths, and the shared review backbone below. Include the shared review backbone in each focused review prompt. Scope by subsystem, changed area, risk dimension, acceptance criterion, cross-cutting impact, or hypothesis. Allow intentional overlap when risk justifies it, but avoid accidental duplicate work. Focused review subagents must not modify source, tests, config, docs, or generated files; they may only write temporary markdown notes/reports.
16
16
 
17
+ 3. Validation:
18
+ Before reporting, challenge each candidate finding against the actual code path and surrounding context. Drop false positives, duplicates, out-of-scope concerns, and issues that rely on unsupported assumptions or are already handled by guards, call sites, defaults, tests, or documented contracts. Keep only material findings with concrete affected behavior and an actionable fix.
19
+
17
20
  Shared review backbone for you and focused review subagents:
18
21
  Put your strict maintainer hat on.
19
22
  Find concrete, high-confidence, material issues introduced by the work or revealed by the additional context.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-review",
3
- "version": "1.1.2",
3
+ "version": "1.1.3",
4
4
  "description": "Review current pi work in a new branch with conversation context",
5
5
  "type": "module",
6
6
  "keywords": [
package/src/index.ts CHANGED
@@ -28,6 +28,9 @@ Delegate tightly scoped repo-local research on relevant pre-existing subsystems,
28
28
  2. Focused review:
29
29
  Delegate one or more scoped reviews using the review surface, relevant reconnaissance note paths, and the shared review backbone below. Include the shared review backbone in each focused review prompt. Scope by subsystem, changed area, risk dimension, acceptance criterion, cross-cutting impact, or hypothesis. Allow intentional overlap when risk justifies it, but avoid accidental duplicate work. Focused review subagents must not modify source, tests, config, docs, or generated files; they may only write temporary markdown notes/reports.
30
30
 
31
+ 3. Validation:
32
+ Before reporting, challenge each candidate finding against the actual code path and surrounding context. Drop false positives, duplicates, out-of-scope concerns, and issues that rely on unsupported assumptions or are already handled by guards, call sites, defaults, tests, or documented contracts. Keep only material findings with concrete affected behavior and an actionable fix.
33
+
31
34
  Shared review backbone for you and focused review subagents:
32
35
  Put your strict maintainer hat on.
33
36
  Find concrete, high-confidence, material issues introduced by the work or revealed by the additional context.