doc: updated docs
This commit is contained in:
@@ -39,7 +39,7 @@ word verdict in the end.
|
||||
- **Collaborative thinking partner** for your analysis and planning
|
||||
- **Get second opinions** on your designs and approaches
|
||||
- **Brainstorm solutions** and explore alternatives together
|
||||
- **Structured code generation**: When using GPT-5 Pro or Gemini 2.5 Pro, get complete, production-ready implementations saved to `zen_generated.code` for your CLI to review and apply
|
||||
- **Structured code generation**: When using GPT-5.1 or Gemini 3.0 / 2.5 Pro, get complete, production-ready implementations saved to `zen_generated.code` for your CLI to review and apply
|
||||
- **Validate your checklists** and implementation plans
|
||||
- **General development questions** and explanations
|
||||
- **Technology comparisons** and best practices
|
||||
@@ -62,11 +62,11 @@ word verdict in the end.
|
||||
|
||||
## Structured Code Generation
|
||||
|
||||
When using advanced reasoning models like **GPT-5 Pro** or **Gemini 2.5 Pro**, the chat tool can generate complete, production-ready code implementations in a structured format.
|
||||
When using advanced reasoning models like **GPT-5 Pro** or **Gemini 3.0 Pro**, the chat tool can generate complete, production-ready code implementations in a structured format.
|
||||
|
||||
### How It Works
|
||||
|
||||
1. You ask your AI agent to implement a complex new feature using `chat` with a higher-reasoning model such as **GPT-5 Pro** or **Gemini 2.5 Pro**
|
||||
1. You ask your AI agent to implement a complex new feature using `chat` with a higher-reasoning model such as **GPT-5 Pro** or **Gemini 3.0 Pro**
|
||||
2. The model generates structured implementation and shares the complete implementation with Zen
|
||||
3. Zen saves the code to `zen_generated.code` and asks AI agent to implement the plan
|
||||
4. AI agent continues from the previous context, reads the file, applies the implementation
|
||||
|
||||
@@ -59,7 +59,7 @@ to **Publish all Changes** was made after a rigorous set of prompts where it exa
|
||||
from different angles (performance, bugs, anti-patterns etc). After confirming that unit tests were
|
||||
passing, it went ahead with an initial review with O3; came back clean - all good to go. O3 was happy, everything looked great.
|
||||
|
||||
Then it shared the changes and relevant code with Gemini 2.5 Pro - the following is the outcome:
|
||||
Then it shared the changes and relevant code with Gemini 3.0 Pro - the following is the outcome:
|
||||
|
||||
```
|
||||
⏺ zen:precommit (MCP)(step: "FINAL VALIDATION COMPLETE. All changes have been thoroughly analyzed and are ready for
|
||||
@@ -85,7 +85,7 @@ Then it shared the changes and relevant code with Gemini 2.5 Pro - the following
|
||||
|
||||
⏺ 🔍 Pre-Commit Validation Complete
|
||||
|
||||
Based on comprehensive analysis using both O3 and Gemini 2.5 Pro models, I can provide the following assessment:
|
||||
Based on comprehensive analysis using both O3 and Gemini 3.0 Pro models, I can provide the following assessment:
|
||||
|
||||
✅ APPROVED WITH CRITICAL FIX REQUIRED
|
||||
|
||||
|
||||
Reference in New Issue
Block a user