@melihmucuk/pi-crew 1.0.16 → 1.0.18

package/README.md

@@ -86,7 +86,7 @@ Note: This prompt requires the `scout` and `planner` subagent definitions. These
 #### `/pi-crew-review`
 
 Expands a bundled prompt template that orchestrates parallel code and quality reviews.
-Use it to review recent commits, staged changes, unstaged changes, and untracked files with `code-reviewer` and `quality-reviewer`, then merge both results into one report.
+Use it to review provided or default changed-code scope with `code-reviewer` and `quality-reviewer`, using compact task-specific briefs focused on intent, expected behavior, and relevant references, then merge both results into one report.
 
 Note: This prompt requires the `code-reviewer` and `quality-reviewer` subagent definitions. These are included as bundled subagents and work out of the box.
 
@@ -94,7 +94,7 @@ Note: This prompt requires the `code-reviewer` and `quality-reviewer` subagent d
 
 #### `pi-crew`
 
-A bundled orchestration skill that provides best practices for delegating work to subagents, handling asynchronous results, and managing interactive subagent lifecycle. It loads automatically when you coordinate work with pi-crew tools.
+A bundled orchestration skill that provides best practices for delegating work to subagents, handling asynchronous results, and managing interactive subagent lifecycle. It also guides compact, task-specific subagent briefs that avoid repeating role boilerplate or mechanical repo/Git state. It loads automatically when you coordinate work with pi-crew tools.
 
 ## Bundled Subagents
 
@@ -102,12 +102,12 @@ pi-crew ships with six subagent definitions that cover common workflows:
 
 | Subagent             | Purpose                                                                                                                  | Tools                      | Model                       |
 | -------------------- | ------------------------------------------------------------------------------------------------------------------------ | -------------------------- | --------------------------- |
-| **scout**            | Investigates codebase and returns structured findings. Read-only. Use before planning or implementing to gather context. | read, grep, find, ls, bash | anthropic/claude-haiku-4-5  |
-| **planner**          | Analyzes requirements and produces a step-by-step implementation plan. Read-only. Does not write code. Interactive.      | read, grep, find, ls, bash | openai-codex/gpt-5.4        |
-| **oracle**           | Evaluates critical decisions, surfaces blind spots, and challenges assumptions. Read-only. Does not implement. Interactive. | read, grep, find, ls, bash | openai-codex/gpt-5.4        |
-| **code-reviewer**    | Reviews code changes for bugs, security issues, and correctness. Read-only. Does not fix issues.                         | read, grep, find, ls, bash | openai-codex/gpt-5.4        |
-| **quality-reviewer** | Reviews code structure for maintainability, duplication, and complexity. Read-only. Does not look for bugs.              | read, grep, find, ls, bash | openai-codex/gpt-5.4        |
-| **worker**           | Implements code changes, fixes, and refactors autonomously. Has full read-write access to the codebase.                  | all                        | anthropic/claude-sonnet-4-6 |
+| **scout**            | Investigates codebase and returns structured findings. Read-only. Use before planning or implementing to gather context. | read, grep, find, ls, bash | openai-codex/gpt-5.5        |
+| **planner**          | Analyzes requirements and produces a step-by-step implementation plan. Read-only. Does not write code. Interactive.      | read, grep, find, ls, bash | openai-codex/gpt-5.5        |
+| **oracle**           | Evaluates critical decisions, surfaces blind spots, and challenges assumptions. Read-only. Does not implement. Interactive. | read, grep, find, ls, bash | openai-codex/gpt-5.5        |
+| **code-reviewer**    | Reviews code changes for bugs, security issues, and correctness. Read-only. Does not fix issues.                         | read, grep, find, ls, bash | openai-codex/gpt-5.2        |
+| **quality-reviewer** | Reviews code structure for maintainability, duplication, and complexity. Read-only. Does not look for bugs.              | read, grep, find, ls, bash | openai-codex/gpt-5.2        |
+| **worker**           | Implements code changes, fixes, and refactors autonomously. Has full read-write access to the codebase.                  | all                        | openai-codex/gpt-5.5        |
 
 Read-only bundled subagents still keep `bash` for inspection workflows like `git` and `ast-grep`. This is an instruction-level contract, not a sandbox boundary.
 

package/agents/code-reviewer.md

@@ -1,7 +1,7 @@
 ---
 name: code-reviewer
 description: Reviews changed code for actionable bugs. Read-only.
-model: openai-codex/gpt-5.4
+model: openai-codex/gpt-5.2
 thinking: high
 tools: read, grep, find, ls, bash
 ---
@@ -14,7 +14,7 @@ Do not modify files. Use bash only for read-only inspection. Do not run builds,
 
 Review the provided scope. If none is provided, review uncommitted changes. For commits, branches, PRs, files, or "latest" requests, inspect the corresponding diff. If "latest" is requested, review the last 5 commits unless a count is given.
 
-If the diff exceeds 500 lines, list changed files with one-line risk notes, then deeply review only the highest-risk files: business logic, auth, data mutation, error handling, public APIs.
+For large or broad diffs, summarize coverage by area with brief risk notes, then deeply review only the highest-risk changed files: business logic, auth, data mutation, error handling, and public APIs. Avoid exhaustive file inventories.
 
 Review changed-code issues only. Pre-existing code is reportable only when the change triggers it or makes it relevant.
 

package/agents/oracle.md

@@ -1,7 +1,7 @@
 ---
 name: oracle
 description: Evaluates critical decisions, surfaces blind spots, and challenges assumptions. Read-only.
-model: openai-codex/gpt-5.4
+model: openai-codex/gpt-5.5
 thinking: xhigh
 tools: read, grep, find, ls, bash
 interactive: true

package/agents/planner.md

@@ -1,7 +1,7 @@
 ---
 name: planner
 description: Produces deterministic implementation plans. Read-only. Does not write code.
-model: openai-codex/gpt-5.4
+model: openai-codex/gpt-5.5
 thinking: high
 tools: read, grep, find, ls, bash
 interactive: true
@@ -50,9 +50,11 @@ Use exactly these sections:
 1. `# Plan – <Short Title>`
 
 2. `## What`
+
 - Brief technical restatement of the change.
 
 3. `## How`
+
 - High-level approach.
 - **Scope**: in scope, out of scope, and scope assumptions.
 - **Assumptions**: list assumptions or `None`.
@@ -60,6 +62,7 @@ Use exactly these sections:
 - Key constraints/trade-offs, only if relevant.
 
 4. `## TODO`
+
 - File-oriented steps in dependency order.
 - Each step starts with `Create`, `Add`, `Update`, `Remove`, `Refactor`, or `Move`.
 - Name the file path and concrete identifiers.
@@ -68,6 +71,7 @@ Use exactly these sections:
 - If TODO exceeds 20 steps, split into phases, mark the first implementation phase, and re-check for scope creep.
 
 5. `## Outcome`
+
 - Expected end state.
 - Functional criteria.
 - Relevant non-functional criteria.

package/agents/quality-reviewer.md

@@ -1,7 +1,7 @@
 ---
 name: quality-reviewer
 description: Reviews changed code for maintainability, duplication, and complexity. Read-only.
-model: openai-codex/gpt-5.4
+model: openai-codex/gpt-5.2
 thinking: high
 tools: read, grep, find, ls, bash
 ---
@@ -18,7 +18,7 @@ Review the provided scope. If none is provided, review uncommitted changes. For
 
 If "full" or "codebase" is requested, first produce a structural risk map, then deeply review only the highest-risk areas.
 
-If the scope exceeds 15 files, summarize files with one-line structural notes, then deeply review the highest-risk files: large files, dependency-heavy files, widely imported files, or files crossing module boundaries. State skipped files briefly.
+For large or broad scopes, summarize coverage by area with brief structural notes, then deeply review the highest-risk areas/files: large files, dependency-heavy files, widely imported files, or files crossing module boundaries. Avoid exhaustive file inventories; state skipped areas briefly.
 
 ## Method
 

package/agents/scout.md

@@ -1,8 +1,8 @@
 ---
 name: scout
 description: Investigates codebase and returns structured findings. Read-only.
-model: anthropic/claude-haiku-4-5
-thinking: minimal
+model: openai-codex/gpt-5.5
+thinking: off
 tools: read, grep, find, ls, bash
 ---
 

package/agents/worker.md

@@ -1,8 +1,8 @@
 ---
 name: worker
 description: Implements scoped code changes safely and verifies them.
-model: anthropic/claude-sonnet-4-6
-thinking: medium
+model: openai-codex/gpt-5.5
+thinking: low
 ---
 
 You are a worker agent. Implement the assigned task or plan as small, safe, verifiable code changes. Reply in the user's language.
@@ -25,7 +25,7 @@ Before changing code, gather enough context to act safely: project conventions,
 
 ## Verification
 
-Run relevant verification: lint, typecheck, tests, and build as applicable. If a relevant check cannot be run, state why.
+Run the smallest meaningful verification for the change; use broader lint, typecheck, tests, or build only when relevant. If a relevant check cannot be run, state why.
 
 Fix only failures caused by your changes. Do not fix pre-existing failures; report them with evidence. If you cannot tell whether a failure is pre-existing or caused by your change, report it as a blocker.