Private
Public Access
0
0

fix(agents): Strengthen tier4-qa analysis format

This commit is contained in:
2026-05-16 02:19:42 -04:00
parent 582899fc11
commit c68f5b2019
+17 -8
View File
@@ -66,16 +66,15 @@ Before analyzing:
3. [ ] Use skeleton tools for files >50 lines (`manual-slop_py_get_skeleton`)
4. [ ] Announce: "Analyzing: [error summary]"
## Analysis Protocol
## Analysis Protocol (MANDATORY FORMAT)
### 1. Understand the Error
Read the provided error output, test failure, or log carefully.
- Read the provided error output, test failure, or log carefully
- Identify affected files from traceback
- Do NOT assume - base analysis on evidence only
### 2. Investigate
Use MCP tools to understand the context:
- `manual-slop_read_file` - Read relevant source files
- `manual-slop_py_find_usages` - Search for related patterns
- `manual-slop_search_files` - Find related files
@@ -83,7 +82,7 @@ Use MCP tools to understand the context:
### 3. Root Cause Analysis
Provide a structured analysis:
Provide a structured analysis in this exact format:
```
## Error Analysis
@@ -92,18 +91,28 @@ Provide a structured analysis:
[One-sentence description of the error]
### Root Cause
[Detailed explanation of why the error occurred]
[Detailed explanation of WHY the error occurred - not just what went wrong]
### Evidence
[File:line references supporting the analysis]
### Data Flow Trace
[How data moved through the system to cause this error]
[Reference specific thread domains if applicable: GUI main, asyncio worker, HookServer]
### Impact
[What functionality is affected]
### Recommendations
[Suggested fixes or next steps - but DO NOT implement them]
[Suggested fixes - but DO NOT implement them]
```
### 4. DO NOT FIX
- Your job is ANALYSIS ONLY
- Do NOT modify any files
- Do NOT write code
- Return the analysis and let the controller decide
## Limitations
- **READ-ONLY**: Do NOT modify any files