pi-pair-programmer 0.1.1 → 0.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.
- package/README.md +6 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -12,6 +12,8 @@ Agents optimize for local correctness instead of thinking about the global syste
|
|
|
12
12
|
Turn-by-turn static analysis is necessary but not sufficient.
|
|
13
13
|
Code review happens too late in the code production pipeline.
|
|
14
14
|
|
|
15
|
+
|
|
16
|
+
|
|
15
17
|
This extension lets you run multiple highly specialized reviewers, each focused on a specific concern, to catch issues static analysis cannot detect as soon as code is generated. Without bloating the context window, thanks to a Jev-based filter that removes inherited and duplicate findings.
|
|
16
18
|
|
|
17
19
|
## Install
|
|
@@ -67,3 +69,7 @@ Use `current` or a `provider/model` identifier. File patterns are relative to yo
|
|
|
67
69
|
|
|
68
70
|
- `/pair-stats`: view review activity, findings, tokens, and estimated costs on demand; missing usage stays unknown.
|
|
69
71
|
- Diagnostics stay in files, never the terminal: OMP uses its native logs; Pi uses `~/.pi/agent/logs/pair-programmer/` (or `$PI_CODING_AGENT_DIR/logs/pair-programmer/`).
|
|
72
|
+
|
|
73
|
+
## How it works
|
|
74
|
+
|
|
75
|
+
|