update_analysis
Update the title, project, overview, summary, or initial request of a code analysis to refine its review context. Omitted fields remain unchanged.
Instructions
Change the title, the project, the overview, the summary or the initial request of an analysis. Right after reading the diff, write the overview (objective, approach, attention_points: your global analysis of the feature) and the summary (the functional changes of the feature, one bullet per change, not one bullet per file). Give at least one field; fields left out are kept.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | New title. | |
| project | No | New project. Project the analysis belongs to: the product or feature name, used as its folder in the GUI. Reuse the exact name of an existing project (see list_analyses) for another analysis of it. | |
| summary | No | Functional changes of the feature, one bullet per change (e.g. "Expired tokens are refreshed once before the request fails"), not one bullet per file. Replaces the whole list; [] clears it. | |
| approach | No | Overview: how the feature achieves it (architecture choices, main flow). Replaces the current approach. | |
| objective | No | Overview: what the feature lets users do, from a functional point of view. When the analysis has no overview yet, give objective and approach together to create it. null removes the whole overview (approach and attention points included). | |
| analysis_id | Yes | Id of the analysis, as returned by create_analysis or list_analyses. | |
| request_text | No | Initial request the feature answers (ticket, user prompt), shown to the reviewer. null removes the request. | |
| request_source | No | Where the initial request comes from, e.g. a ticket id or URL. null clears it. | |
| attention_points | No | Overview: risks and points the reviewer should check first, one per string. Replaces the whole list; [] clears it. Defaults to an empty list when the overview is created without it. |