← ClaudeAtlas

gitlab-vuln-remediationlisted

Use when remediating a security finding — SAST, SCA / dependency scanning, or secret detection — including fixing a vulnerability, bumping a dependency for security reasons, removing a hardcoded secret, triaging a false positive, or opening the merge request for any of these. Applies whenever a CVE ID, CWE ID, OWASP category, scanner output (GitLab SAST, Semgrep, Gitleaks, Dependency Scanning), or a `mcp__gitlab-security__*` tool is involved, even if GitLab is not named. Also triggers on "resolve this finding", "open an MR for this CVE", "remediate this vulnerability".
slackwero/skills · ★ 0 · Code & Development · score 46
Install: claude install-skill slackwero/skills
# GitLab Vulnerability Remediation This skill governs how to remediate vulnerabilities detected by GitLab scanners (SAST, SCA / Dependency Scanning, Secret Detection). The goal is to produce **safe, scoped, atomic merge requests** that fix the finding without introducing new vulnerabilities, without changing business logic, and without leaking sensitive data. The skill body covers the shared workflow, principles, and routing. Type-specific rules live in: - `references/sca-remediation.md` — dependency bumps, lockfiles, transitive handling per ecosystem - `references/sast-remediation.md` — canonical fix patterns per CWE across Python, Node.js/TS, Java/Kotlin, Go - `references/secrets-remediation.md` — migration to environment variables and mandatory rotation flagging - `references/mr-template.md` — MR description templates per vulnerability type Read the relevant reference file in full **before** writing any code change. --- ## Core Principles These principles are non-negotiable because each one corresponds to a real failure mode this skill exists to prevent. 1. **Atomic MRs.** One vulnerability per MR — or one coherent group (same CVE across multiple files of the same repo). Bundling unrelated fixes makes review impossible and rollback dangerous. 2. **Minimal blast radius.** Touch only what is required to fix the finding. Do not reformat surrounding code, do not "clean up while we're here", do not rename unrelated symbols. Reviewers should be able to spot the security