Format SEI CERT findings as a report
format_findingsFormats CERT code review findings as Markdown, GitHub, GitLab, SARIF, or Code Quality payloads without posting, enabling draft review before submission.
Instructions
Render findings as a report or review payload without sending it. style: markdown (string); github (object for POST /repos/{owner}/{repo}/pulls/{n}/reviews, event COMMENT, one comment per finding); gitlab (array of merge-request discussion bodies; position SHAs are placeholders to fill from diff_refs); sarif (SARIF 2.1.0 object); codequality (GitLab Code Quality array); gitlab-sast (GitLab SAST report object). Use as the last step, then show drafted comments to the user before anyone posts them. Pass findings unchanged from check_files/check_diff findings or validate_findings accepted. Pure formatting: no files, network or posting.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"findings": "<findings>"
},
"name": "format_findings"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| root | No | Absolute repository root; file paths in the output are made relative to it. Omit and paths become relative to the server's working directory. | |
| style | No | Output format; see the tool description for each shape. | markdown |
| findings | Yes | Findings exactly as returned by check_files, check_diff (findings) or validate_findings (accepted). | |
| warnings | No | `warnings` from check_files/check_diff; shown as a partial-analysis notice in markdown, github and sarif. |