Scan git history and working trees for committed secrets and insecure secret practices.
npx skills add https://github.com/eriknovak/ErikNovak --skill secrets
Please help me install this Agent Skill. Skill: secrets Source: https://github.com/eriknovak/ErikNovak/tree/main/.dotfiles/.claude/skills/secrets Command: npx skills add https://github.com/eriknovak/ErikNovak --skill secrets
Audits codebases for secret handling issues, helping teams detect leaked credentials, misconfigurations in environment management, and insecure patterns early in the development lifecycle.
Audit secrets in your repository by instructing Claude to examine code for exposure patterns and misconfigurations.
High-intent search queries and answers about installing and using this skill.
Scanning for committed secrets involves checking both git history and the current working tree to detect leaked credentials. This audit identifies hardcoded secret patterns and insecure practices, delivering a structured risk report with remediation guidance.
Gitignore validation checks that sensitive files like .env, keys, and credentials are properly ignored. The audit surfaces gitignore gaps where secret files might be accidentally committed, ensuring misconfigurations in environment management are caught early.
Yes, hardcoded secret detection works across repositories of varying languages and sizes. The scan identifies credentials directly in source code and provides guidance for remediation and safe handling of those exposed secrets.
An .env.example or .env.template documents required environment variables without exposing actual secrets. The audit performs template verification to ensure these files exist when .env usage is present, preventing configuration gaps for new developers.
The secret audit performs both history-wide and working-tree checks. This dual approach detects leaked credentials committed in previous commits as well as hardcoded secret patterns currently present in the active codebase.
The audit focuses on detecting committed secrets, gitignore gaps, env template presence, and hardcoded patterns. It does not alter or remove secrets automatically; it delivers structured risk reports with remediation guidance that developers must act on manually.
mattbobambroseDetect committed secrets and sensitive files in git history and working tree.
Greenmamba29Scan environment files and codebases for exposed secrets and generate a remediation report.
rarestgAutomate code quality tooling setup for Python and JavaScript/TypeScript projects.
martinholovskyManage and audit software secret lifecycles with automated leak detection.
