secret-scanning

Detect secrets and PII in code, configurations, and commit history using pattern tables.

Updated Mar 31, 2026

Search Tags:#remediation #compliance #patterns #secrets #pii #code-scanning #version-control

Ready to run

npx skills add https://github.com/shellicar/skills --skill secret-scanning-shellicar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: secret-scanning
Source: https://github.com/shellicar/skills/tree/main/skills/secret-scanning
Command: npx skills add https://github.com/shellicar/skills --skill secret-scanning-shellicar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detects secrets and PII in code and commits using defined pattern tables, with a mandatory per-finding disposition process. Every finding must be explicitly resolved: no silent dismissal, no invented patterns. Without it, secrets enter commits unreported, findings get assumed safe without review, and pattern improvisation floods the report with false positives.

TRIGGER when writing code or config, committing, or pushing.

Core Features & Use Cases

Pattern tables for detecting secrets and PII, safe placeholder values, and the mandatory disposition process for evaluating matches.
Per-finding citation requirement and explicit remediation guidance.
Triggered on write, commit, and push to ensure continuous compliance.

Quick Start

Run the secret-scanning workflow to detect secrets and PII in your repository and enforce explicit disposition for every finding.

Frequently Asked Questions about secret-scanning

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

FAQPage Schema

How do I scan code and commit history for secrets and PII?▼

Scanning code and commit history for secrets and PII uses defined pattern tables during writing, committing, and pushing to detect matches, enforce mandatory disposition, and require explicit remediation for every finding.

How do I prevent false positives when scanning for secrets in code?▼

Preventing false positives during secret scanning requires a mandatory per-finding disposition process with citation requirements and dedicated pattern references, avoiding pattern improvisation and ensuring no silent dismissals without explicit review.

Does secret scanning work during the writing and committing phases?▼

Secret scanning triggers during writing code, committing, and pushing to ensure continuous compliance and detect secrets or PII early using pattern tables and mandatory disposition workflows.

What is the mandatory disposition process for detected secrets?▼

The mandatory disposition process for detected secrets requires every finding to be explicitly resolved with per-finding citation and remediation guidance, preventing invented patterns and ensuring no match is assumed safe without review.

Can I use safe placeholder values when remediating detected secrets?▼

Remediating detected secrets supports safe placeholder values provided through pattern tables, guiding replacement workflows while maintaining compliance and ensuring explicit disposition for every detected PII or secret finding.

How do I expand pattern coverage for detecting different types of secrets?▼

Expanding pattern coverage for detecting secrets uses dedicated pattern references that extend detection tables, allowing you to catch additional PII and secret formats while maintaining the mandatory disposition process for every finding.