pi-review 1.0.0 → 1.0.1

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.
@@ -1 +1 @@
1
- {"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,+BAA+B,CAAC;AA8ClE,MAAM,CAAC,OAAO,UAAU,eAAe,CAAC,EAAE,EAAE,YAAY,QA8CvD"}
1
+ {"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,+BAA+B,CAAC;AAgDlE,MAAM,CAAC,OAAO,UAAU,eAAe,CAAC,EAAE,EAAE,YAAY,QA8CvD"}
package/dist/index.js CHANGED
@@ -4,6 +4,8 @@ const REVIEW_THINKING_LEVEL = "high";
4
4
  const REVIEW_INSTRUCTION = `Review the available work and context.
5
5
  Put your strict maintainer hat on.
6
6
  Find concrete, high-confidence, material issues introduced by the work or revealed by the additional context.
7
+ Do not stop after the first few findings; keep reviewing until you have checked the full diff/context, then do one final pass specifically for issues you may have missed.
8
+ Verify completeness against the stated task, requirements, and acceptance criteria; flag missing or partially implemented requirements as findings.
7
9
  Focus on correctness, security, performance, operability, and maintainability.
8
10
  Do not speculate; point to the affected behavior, invariant, or code path.
9
11
  Prefer issues the author would likely fix before merge.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-review",
3
- "version": "1.0.0",
3
+ "version": "1.0.1",
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
@@ -10,6 +10,8 @@ type ThinkingLevel = ReturnType<ExtensionAPI["getThinkingLevel"]>;
10
10
  const REVIEW_INSTRUCTION = `Review the available work and context.
11
11
  Put your strict maintainer hat on.
12
12
  Find concrete, high-confidence, material issues introduced by the work or revealed by the additional context.
13
+ Do not stop after the first few findings; keep reviewing until you have checked the full diff/context, then do one final pass specifically for issues you may have missed.
14
+ Verify completeness against the stated task, requirements, and acceptance criteria; flag missing or partially implemented requirements as findings.
13
15
  Focus on correctness, security, performance, operability, and maintainability.
14
16
  Do not speculate; point to the affected behavior, invariant, or code path.
15
17
  Prefer issues the author would likely fix before merge.