Skip to content
Skills Library
Security · Automation

sast-integration

/sast-integration

Wire a static analysis scanner into CI so it blocks real security bugs while staying under a defined noise budget. Use when adding a SAST tool to a pipeline or when an existing one is being ignored.

Repository
AI-SKILLS ↗
Licence
MIT
Last repository change
05.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Wire a static analysis scanner into CI so it blocks real security bugs while staying under a defined noise budget. Use when adding a SAST tool to a pipeline or when an existing one is being ignored.

Original author description

Wire a static analysis scanner into CI so it blocks real security bugs while staying under a defined noise budget. Use when adding a SAST tool to a pipeline or when an existing one is being ignored.

How it works

  1. Method
  2. Signals
  3. Boundaries
Original SKILL.md headings · 49 lines, 427 words
SKILL.md preview
---
name: sast-integration
description: Wire a static analysis scanner into CI so it blocks real security bugs while staying under a defined noise budget. Use when adding a SAST tool to a pipeline or when an existing one is being ignored.
---

# SAST integration

Static analysis earns its place only when developers trust its output. A scanner
that dumps 400 findings on every pull request gets muted inside a week, and it
drags the three real bugs down with it. The problem is not running the tool; it
is keeping the signal high enough that people keep reading it.

## Method

1. **Match the scanner to the stack.** Semgrep for polyglot and custom rules,
   CodeQL for deep dataflow, Bandit for Python, gosec for Go, Snyk or
   `npm audit` for dependencies. Turn on the security ruleset, not the full
   style-and-lint pile that buries security findings in formatting noise.
2. **Baseline the existing code first.** Snapshot current findings and suppress
   them as a known baseline so the pipeline reports only what a change adds. A
   greenfield gate pointed at a legacy repo fails on day one and is switched off
   by day two.
3. **Set a noise budget and measure against it.** Target well under one
   developer-facing finding per ten reviewed pull requests. If the false
   positive rate climbs past roughly 20 percent, tune or cut rules before
   adding any: track the number, do not eyeball it.
4. **Gate only on high-confidence, high-severity.** Block on Critical and High
   at high confidence; render Medium and Low as inline annotations that do not
   stop the merge. A noisy blocking gate only trains people to hit the override.
5. **Make every suppression explicit and reviewed.** Require an inline comment
   with a reason (`// nosemgrep: reason`) or a tracked exception, never a
   blanket config exclusion. Suppressions expire or get audited so they cannot
   silently harden into blind spots.
6. **Scan diffs on every PR, the full repo on a schedule.** Analyze only changed
   files per pull request for fast feedback; run the deep full-repo scan nightly
   or weekly and route those results to a backlog, not the blocking gate.
7. **Deliver findings where they get fixed.** Post them as annotations on the
   exact line in the pull request, not to a dashboard nobody opens, and feed
   dependency alerts into the same triage flow.

## Signals

- What fraction of the last 50 findings were acted on rather than dismissed?
- Does a clean pull request ever get blocked by an unrelated legacy finding?
- Can a developer see, and defend, every suppression in the file they touched?

## Boundaries

SAST catches pattern-matchable bugs and misses the business-logic and
authorization flaws that need security-code-review. Which individual rules to
enable is per-repo tuning; this skill fixes the budget and the gating policy,
not the rule list.

Versions

RepositoryScoreLicence
This page · Amey-Thakur/AI-SKILLS90MIT
selvarajmurugesan90/ops-engineering-skills100Apache-2.0

Database snapshot: 13.11.2026 · package version 45f6b1227fc8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90sast-review
    Run or ingest static application security testing (SAST) results on a codebase, triage them to remove false positives, and confirm the real issues with code evidence and remediation. Use when reviewing source code for security flaws or cleaning up noisy scanner output.
  • 100secure-code-review-static-analysis-sast
    Use this skill when audit source code for security vulnerabilities using automated SAST tools and manual inspection.
  • 100llm-sast-scanner
    General-purpose static application security testing (SAST) for any language or framework, covering 34 vulnerability classes across web, API, auth, mobile and logic layers. Use for 'analyze code for vulnerabilities', 'find security bugs', 'do a SAST scan', 'audit source code',…
  • 90sast-scan
    Design a SAST/DAST scanning pipeline — tooling selection, CI integration, and triage workflow. Use when asked to "set up SAST in CI", "add DAST scanning", or "build a security scanning pipeline".
  • 100sast-configuration
    Static Application Security Testing (SAST) configuration skill. Use when setting up security scanning, configuring Semgrep rules, running SAST in CI/CD, reviewing SAST findings, or writing custom security rules. Triggers: SAST, static analysis, Semgrep, Bandit, ESLint security,…
  • 95sast-patterns
    Static Application Security Testing patterns, OWASP Top 10 checklist, language-specific vulnerability patterns, Semgrep rule writing guide, and CI/CD integration. Use when scanning code for security vulnerabilities or writing custom SAST rules.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.