accept_finding
Mark a security finding as a false positive or accepted risk with a documented reason and reviewer. Write a structured suppression comment into the file, with optional expiry for accepted risks.
Instructions
Insert a justified suppression comment into a skill file.
Marks a finding as a false positive or accepted risk with a documented reason, reviewer, and optional expiry date. The suppression is written directly into the file as a structured comment that lives in version control and shows up in PR reviews.
Accepted risks with an expiry date automatically resurface as active findings on the next scan after the expiry date passes.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ave_id | Yes | AVE ID to suppress (e.g. AVE-2026-00001) | |
| file_path | Yes | Absolute or relative path to the skill file | |
| line | Yes | Line number of the finding to suppress | |
| reason | Yes | Why this finding is a false positive or accepted risk | |
| reviewer | Yes | Your GitHub handle or name | |
| acceptance_type | No | "false-positive" (permanent) or "accepted-risk" (with expiry) | false-positive |
| expires_days | No | Days until the accepted risk expires (required for accepted-risk) |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |