SAST Triage

Triage gosec, golangci-lint, and govulncheck findings by severity and false positives.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/cdalsoniii/brightpath-coder --skill sast-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: SAST Triage
Source: https://github.com/cdalsoniii/brightpath-coder/tree/main/.cursor/skills/sast-triage
Command: npx skills add https://github.com/cdalsoniii/brightpath-coder --skill sast-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of triaging static analysis security testing (SAST) findings, helping to distinguish genuine vulnerabilities from false positives and prioritize remediation efforts.

Core Features & Use Cases

  • Automated Triage: Classifies findings by severity (Critical, High, Medium, Low, FalsePositive).
  • False Positive Filtering: Identifies and filters out non-actionable findings.
  • Prioritization: Assigns remediation priority and estimates effort.
  • Use Case: After a CI pipeline runs security scans, this Skill can automatically process the results, flag critical vulnerabilities, and provide developers with a clear, actionable list of issues to address.

Quick Start

Use the SAST Triage skill to classify security findings from the latest gosec scan results.

Frequently Asked Questions about SAST Triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage gosec and govulncheck findings to filter false positives?

Triage static analysis security findings by classifying severity, filtering false positives, and mapping results to CWE/CVE identifiers. This Skill processes outputs from gosec, golangci-lint, and govulncheck to distinguish genuine vulnerabilities from non-actionable noise.

What is the best way to prioritize Go security vulnerabilities from SAST scans?

Prioritize Go security vulnerabilities by estimating remediation effort and assigning priority based on severity classification. The Skill evaluates SAST scan results to provide developers with an actionable list of issues sorted by criticality.

Do I need shell access to run golangci-lint security checks for triage?

Yes, you need shell access to execute SAST tools like golangci-lint, gosec, and govulncheck. The Skill also requires read access to Go source files and SAST output, plus write access to generate triage reports.

Can I automatically classify SAST findings by severity in my CI pipeline?

You can automatically classify SAST findings by severity in a CI pipeline. After security scans complete, the Skill processes results to flag critical vulnerabilities and categorize findings as Critical, High, Medium, Low, or FalsePositive.

How does mapping security findings to CWE and CVE identifiers help with remediation?

Mapping security findings to CWE and CVE identifiers helps with remediation by providing standardized vulnerability references. This allows the Skill to accurately filter false positives and prioritize genuine issues based on their specific vulnerability classifications.

What are the limitations of automating SAST triage for Go source files?

Automating SAST triage for Go source files is limited to processing outputs from gosec, golangci-lint, and govulncheck. The Skill requires direct read access to source files and cannot triage findings from unsupported static analysis tools.