Add Zed AI Agent System Prompt

[IgorWarzocha]

Summary

• Add complete Zed editor AI agent system prompt template
• Includes unique path-based code block formatting requirement
• Features Handlebars template variables for dynamic content
• Covers tool usage guidelines and communication style

Summary by CodeRabbit

• Chores
  • Added system configuration file with guidelines and formatting standards.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A new system prompt file has been added to the Zed directory, containing comprehensive guidelines for assistant behavior including code block formatting requirements, tool usage rules, path resolution strategies, and diagnostic fixing approaches.

Changes

Cohort / File(s)	Change Summary
System Prompt Configuration Zed/System Prompt.txt	New file added with complete system prompt encompassing communication style, code block formatting rules (path-based with line ranges), conditional tool-use sections, file path resolution guidelines, debugging practices, and templates for correct and incorrect code formatting.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

• Review focuses on clarity and correctness of guidelines rather than code logic verification
• Single, self-contained configuration file with no external dependencies or interactions
• Verify that formatting rules and examples are consistent and unambiguous
• Check that conditional sections and metadata placeholders are properly structured for integration into the system

Poem

🐇 A prompt so grand, with rules so clear,
Code blocks and paths, the way forward's here,
Tools and diagnostics, all in their place,
Guidelines guide us with measured grace,
Zed's wisdom captured, precise and neat! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add Zed AI Agent System Prompt' directly and clearly describes the main change: adding a new system prompt file for Zed's AI agent, which aligns with the PR objective and the new file addition.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b77ac4d and 748b6f8.

📒 Files selected for processing (1)

• Zed/System Prompt.txt (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: thedtvn
Repo: x1xhlol/system-prompts-and-models-of-ai-tools PR: 307
File: Grok/Ani.md:35-35
Timestamp: 2025-11-20T11:10:16.052Z
Learning: In the repository x1xhlol/system-prompts-and-models-of-ai-tools, files contain system prompts extracted via reverse engineering or MITM attacks from AI tools. These prompts should be preserved exactly as found, including any malformed tags, unusual formatting, or apparent errors, as they represent the authentic source material.

📚 Learning: 2025-11-20T11:10:16.052Z

Learnt from: thedtvn
Repo: x1xhlol/system-prompts-and-models-of-ai-tools PR: 307
File: Grok/Ani.md:35-35
Timestamp: 2025-11-20T11:10:16.052Z
Learning: In the repository x1xhlol/system-prompts-and-models-of-ai-tools, files contain system prompts extracted via reverse engineering or MITM attacks from AI tools. These prompts should be preserved exactly as found, including any malformed tags, unusual formatting, or apparent errors, as they represent the authentic source material.

Applied to files:

• Zed/System Prompt.txt

🪛 LanguageTool

Zed/System Prompt.txt

[uncategorized] ~7-~7: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ...rst person. 3. Format your responses in markdown. Use backticks to format file, director...

(MARKDOWN_NNP)

---

[style] ~57-~57: As an alternative to the over-used intensifier ‘really’, consider replacing this phrase.
Context: ...ll have to do it over again. Just to be really clear about this, if you ever find yourself w...

(EN_WEAK_ADJECTIVE)

---

[grammar] ~144-~144: Use a hyphen to join words.
Context: ...itly requested by the user, use the best suited external APIs and packages to sol...

(QB_NEW_EN_HYPHEN)

🔇 Additional comments (1)

Zed/System Prompt.txt (1)

1-188: Approved: Comprehensive Zed system prompt with proper structure and Handlebars templating.

The system prompt is well-structured and complete, with properly balanced conditional logic for handling scenarios with and without tools. The path-based code block formatting specification (lines 48-125) is clearly documented with explicit examples of both correct and incorrect usage. All Handlebars template syntax is properly closed and should render correctly.

Static analysis flagged minor style suggestions at lines 7 ("markdown" capitalization), 57 ("really" intensifier), and 144 ("best suited" hyphenation). However, per learnings from this repository, system prompts should be preserved exactly as extracted from the source material, including any minor style variations. These suggestions should not be applied.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}