You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"The sequence below contains NEW execution steps that have occurred SINCE the existing guide was written.\n"
180
+
)
181
+
165
182
return (
166
-
"You are an expert AI architect summarizing system behavior.\n"
167
-
"Analyze the following machine-generated execution logs and convert them "
168
-
"into a single, coherent, human-readable summary of the actions taken and the rationale behind them. "
169
-
"Focus on the 'why' and 'what'. Keep it concise but highly informative.\n\n"
170
-
f"Logs:\n{raw_text}\n\nSummary:"
183
+
"You are an expert Software Architect and Technical Documentation Specialist with 15+ years of experience. \n"
184
+
"You excel at turning raw execution traces, command sequences, API calls, tool invocations, and successful action chains into clear, professional, human-readable procedural guides.\n\n"
185
+
"TASK:\n"
186
+
"Analyze the following procedural log/sequence of successful actions and transform it into a coherent, easy-to-follow step-by-step instruction guide for a developer or engineer.\n\n"
187
+
f"{context_part}"
188
+
"REQUIREMENTS:\n"
189
+
"- Identify the overall purpose and final outcome.\n"
190
+
"- Break everything into logical, numbered steps.\n"
191
+
"- For each step clearly state:\n"
192
+
" • WHAT is done\n"
193
+
" • WHY it is done (technical or business reason)\n"
194
+
"- Show dependencies and flow between steps.\n"
195
+
"- Remove noise, abstract technical details where possible, but keep important parameters and outcomes.\n"
196
+
"- Use concise, professional language.\n"
197
+
"- IMPORTANT: If previous context is provided, INTEGRATE the new steps into the existing guide. Re-order, group, or refine the steps to maintain a logical and coherent flow. Update the 'Overall Objective' if needed.\n\n"
198
+
"OUTPUT FORMAT (strictly follow this structure):\n\n"
199
+
"1. **Overall Objective**\n"
200
+
" One-sentence summary of what this procedure achieves.\n\n"
201
+
"2. **Prerequisites** (if any)\n\n"
202
+
"3. **Step-by-Step Procedure**\n"
203
+
" 1. [Step description]\n"
204
+
" • What: ...\n"
205
+
" • Why: ...\n"
206
+
" • Key details/parameters: ...\n\n"
207
+
"4. **Key Insights & Recommendations**\n"
208
+
" Any architectural observations, potential improvements, or best practices.\n\n"
"The logs below are NEW activities that have occurred SINCE the previous summary.\n"
225
+
)
226
+
174
227
return (
175
-
"You are an expert AI architect analyzing behavioral patterns in a codebase.\n"
176
-
f"I have detected a high density of activity related to the component '{target}'.\n"
177
-
"Based on the following execution logs, please provide a high-level summary of what the developer/agent "
178
-
"has been working on in this area. Identify the main theme, goal, or technical shift reflected in these actions.\n\n"
179
-
f"Logs:\n{logs[:5000]}\n\nSummary of Behavioral Pattern:"
228
+
"You are a Principal Engineer and Codebase Archaeologist specializing in reverse-engineering developer intent from activity clusters.\n\n"
229
+
"TASK:\n"
230
+
"You are given a dense cluster of NEW events, logs, commits, or activities concentrated around a specific component, module, file, or target. \n"
231
+
f"Analyze this high-density activity zone for '{target}' and extract the underlying technical shift, main goal, and behavioral pattern of the developer/team.\n\n"
232
+
f"{context_part}"
233
+
"REQUIREMENTS:\n"
234
+
"- Identify the primary technical evolution or refactoring direction.\n"
235
+
"- Uncover the core objective (what problem is being solved or opportunity pursued).\n"
236
+
"- Detect recurring patterns in the work style or architectural decisions.\n"
237
+
"- Base every conclusion on concrete evidence from the provided cluster.\n"
238
+
"- IMPORTANT: If previous context is provided, INTEGRATE the new findings into a single, updated, and coherent summary. Refine the technical shift and goal if the new logs provide more clarity.\n\n"
239
+
"OUTPUT FORMAT (strictly follow this structure):\n\n"
240
+
"1. **Detected Technical Shift**\n"
241
+
" One-sentence summary of the main change happening.\n\n"
242
+
"2. **Primary Goal / Intent**\n"
243
+
" What the developer is ultimately trying to achieve.\n\n"
244
+
"3. **Key Patterns Observed**\n"
245
+
" • Pattern 1: description + evidence\n"
246
+
" • Pattern 2: ...\n\n"
247
+
"4. **Architectural & Strategic Implications**\n"
248
+
" How this activity affects the larger codebase and possible next steps or risks.\n\n"
249
+
"5. **Component Evolution Summary**\n"
250
+
" Brief before → after picture (if inferable).\n\n"
251
+
"Now analyze this NEW activity cluster:\n\n"
252
+
f"{logs[:5000]}\n\nUpdated Summary of Behavioral Pattern:"
0 commit comments