secret-scan-triage

Installation
SKILL.md

Secret scan triage

Use this skill when gitleaks findings need a disciplined triage path so real exposures are contained quickly and false positives are handled without weakening scanning.

Use this skill when

  • gitleaks reports findings in local hooks, CI, or a manual scan.
  • A branch is blocked by secret scan failures and needs evidence-based triage.
  • You need to separate real credential exposure from known-safe test fixtures or synthetic tokens.
  • You need a consistent remediation path that preserves scanning quality.

Do not use this skill when

  • The task is implementing a new scanner or replacing the security toolchain.
  • There are no scan findings and the ask is general security hardening.
  • The user explicitly requests incident response actions outside repository scope.

Routing boundary

Installs
7
GitHub Stars
4
First Seen
Sep 1, 2026