mirror of
https://github.com/Aider-AI/aider.git
synced 2025-05-30 17:24:59 +00:00
Summarization prompt for aider
feat: Add local_analytics/ to .gitignore
This commit is contained in:
parent
3caab85931
commit
4e0964046a
2 changed files with 42 additions and 12 deletions
1
.gitignore
vendored
1
.gitignore
vendored
|
@ -16,3 +16,4 @@ aider/_version.py
|
||||||
.#*
|
.#*
|
||||||
.gitattributes
|
.gitattributes
|
||||||
tmp.benchmarks/
|
tmp.benchmarks/
|
||||||
|
local_analytics/
|
||||||
|
|
|
@ -46,19 +46,48 @@ And got this output:
|
||||||
"""
|
"""
|
||||||
|
|
||||||
# CHAT HISTORY
|
# CHAT HISTORY
|
||||||
summarize = """*Briefly* summarize this partial conversation about programming.
|
# summarize = """*Briefly* summarize this partial conversation about programming.
|
||||||
Include less detail about older parts and more detail about the most recent messages.
|
# Include less detail about older parts and more detail about the most recent messages.
|
||||||
Start a new paragraph every time the topic changes!
|
# Start a new paragraph every time the topic changes!
|
||||||
|
|
||||||
This is only part of a longer conversation so *DO NOT* conclude the summary with language like "Finally, ...". Because the conversation continues after the summary.
|
# This is only part of a longer conversation so *DO NOT* conclude the summary with language like "Finally, ...". Because the conversation continues after the summary.
|
||||||
The summary *MUST* include the function names, libraries, packages that are being discussed.
|
# The summary *MUST* include the function names, libraries, packages that are being discussed.
|
||||||
The summary *MUST* include the filenames that are being referenced by the assistant inside the ```...``` fenced code blocks!
|
# The summary *MUST* include the filenames that are being referenced by the assistant inside the ```...``` fenced code blocks!
|
||||||
The summaries *MUST NOT* include ```...``` fenced code blocks!
|
# The summaries *MUST NOT* include ```...``` fenced code blocks!
|
||||||
|
|
||||||
Phrase the summary with the USER in first person, telling the ASSISTANT about the conversation.
|
# # Phrase the summary with the USER in first person, telling the ASSISTANT about the conversation.
|
||||||
Write *as* the user.
|
# # Write *as* the user.
|
||||||
The user should refer to the assistant as *you*.
|
# # The user should refer to the assistant as *you*.
|
||||||
Start the summary with "I asked you...".
|
# # Start the summary with "I asked you...".
|
||||||
|
# # """
|
||||||
|
|
||||||
|
|
||||||
|
#GEMINI SPECIFIC
|
||||||
|
summarize = """
|
||||||
|
You are a Conversation Summarizer for partial conversation about programming.
|
||||||
|
|
||||||
|
INPUT:
|
||||||
|
- A concatenated string representing a segment of conversation history. Each message is prefixed with `# USER` or `# ASSISTANT`.
|
||||||
|
|
||||||
|
OUTPUT:
|
||||||
|
- A SINGLE STRING containing a concise summary of the input conversation segment.
|
||||||
|
- Your response MUST contain ONLY this single summary string. Do NOT include any other text, explanations, or code blocks.
|
||||||
|
|
||||||
|
INSTRUCTIONS:
|
||||||
|
1. Analyze the provided conversation segment.
|
||||||
|
2. Condense the essential information into a concise summary string.
|
||||||
|
3. Prioritize details from messages occurring later in the sequence.
|
||||||
|
4. Include key technical elements: filenames, function names, commands executed, outcomes of actions (like test results or errors), libraries, packages, code changes discussed, and decisions made about the technical approach.
|
||||||
|
5. Omit conversational filler, greetings, and non-essential discussion.
|
||||||
|
6. Do NOT include ```...``` fenced code blocks or any other markdown formatting in your output string.
|
||||||
|
|
||||||
|
SUMMARY CRITERIA:
|
||||||
|
- Goal: Provide maximum relevant technical context for another LLM (a code editor) to understand project state and recent actions within this segment.
|
||||||
|
- Prioritization: Technical precision and action outcomes > Exhaustive completeness of discussion.
|
||||||
|
- Style: Action-focused, highlighting code changes, command executions, and technical decisions.
|
||||||
|
|
||||||
|
Conversation Segment to Summarize:
|
||||||
|
{{CONVERSATION_SEGMENT}}
|
||||||
"""
|
"""
|
||||||
|
|
||||||
summary_prefix = "I spoke to you previously about a number of things.\n"
|
summary_prefix = "I spoke to you previously about a number of things.\n"
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue