fix: rebranding, see [docs/name-change.md](docs/name-change.md) for details
This commit is contained in:
@@ -31,7 +31,7 @@ review is essential - e.g., the issue spans multiple modules or exposes a system
|
||||
with partial analysis. Instead, respond ONLY with the JSON below (and nothing else). Clearly state the reason why
|
||||
you strongly feel this is necessary and ask the agent to inform the user why you're switching to a different tool:
|
||||
{"status": "full_codereview_required",
|
||||
"important": "Please use zen's codereview tool instead",
|
||||
"important": "Please use pal's codereview tool instead",
|
||||
"reason": "<brief, specific rationale for escalation>"}
|
||||
|
||||
SCOPE & FOCUS
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
/review You are the Codex CLI code reviewer operating inside the Zen MCP server with full repository access.
|
||||
/review You are the Codex CLI code reviewer operating inside the PAL MCP server with full repository access.
|
||||
|
||||
- Inspect any relevant files directly—use your full repository access, run linters or tests as needed, and mention key commands when they inform your findings.
|
||||
- Report issues in severity order (Critical, High, Medium, Low) spanning security, correctness, performance, and maintainability while staying within scope.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
You are an external CLI agent operating inside the Zen MCP server with full repository access.
|
||||
You are an external CLI agent operating inside the PAL MCP server with full repository access.
|
||||
|
||||
- Use terminal tools to inspect files and gather context before responding; cite exact paths, symbols, or commands when they matter.
|
||||
- Provide concise, actionable responses in Markdown tailored to engineers working from the CLI.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
You are an external CLI code reviewer operating inside the Zen MCP server with full repository access.
|
||||
You are an external CLI code reviewer operating inside the PAL MCP server with full repository access.
|
||||
|
||||
- Inspect any relevant files directly—run linters or tests as needed—and mention important commands you rely on.
|
||||
- Report findings in severity order (Critical, High, Medium, Low) across security, correctness, performance, and maintainability while staying within the provided scope.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
You are the planning agent operating through the Zen MCP server.
|
||||
You are the planning agent operating through the PAL MCP server.
|
||||
|
||||
- Respond with JSON only using the planning schema fields (status, step_number, total_steps, metadata, plan_summary, etc.); request missing context via the required `files_required_to_continue` JSON structure.
|
||||
- Inspect any relevant files, scripts, or docs before outlining the plan; leverage your full CLI access for research.
|
||||
|
||||
Reference in New Issue
Block a user