Secrets Review

Name: Secrets Review
Availability: InStock
Author: lazyninja435

Detect accidentally committed secrets and credentials across codebases and git history.

1|Updated Jun 3, 2026

Search Tags:#git #security #audit #compliance #secrets #credentials

Ready to run

npx skills add https://github.com/LazyNinja435/astrai --skill secrets-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Secrets Review
Source: https://github.com/LazyNinja435/astrai/tree/main/.ai/skills/security/secrets-review
Command: npx skills add https://github.com/LazyNinja435/astrai --skill secrets-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies accidentally committed secrets, API keys, and sensitive credentials within your codebase, preventing potential security breaches and unauthorized access.

Core Features & Use Cases

Pattern Scanning: Detects common API key formats, tokens, and private keys across the entire repository.
Configuration Audit: Scans environment files and configuration files for hardcoded sensitive data.
Use Case: Before pushing code to a public repository, run this skill to ensure no development or production secrets are leaked in the commit history.

Quick Start

Use the secrets review skill to scan the entire repository for any hardcoded credentials or sensitive tokens.

Frequently Asked Questions about Secrets Review

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

FAQPage Schema

How do I scan my git history for accidentally committed secrets and API keys?▼

Scanning git history for committed secrets involves running pattern matching and heuristic analysis across your repository. This skill identifies hardcoded credentials, API keys, and tokens within source files and commit logs to ensure security compliance.

How do I audit environment configuration files for hardcoded credentials?▼

Auditing environment configuration files for hardcoded credentials requires scanning your config files for sensitive data. This skill performs configuration audits to detect common API key formats, private keys, and tokens across your codebase.

What is the best way to check a codebase for exposed credentials before pushing to a public repository?▼

Checking a codebase for exposed credentials before a public push requires a comprehensive security audit. This skill scans source files and git history using pattern matching to detect potential leaks and provides remediation guidance.

Can I detect sensitive data leaks across my entire source files and git history?▼

You can detect sensitive data leaks across source files and git history by applying heuristic analysis to your repository. This skill flags accidentally committed secrets and sensitive configurations to prevent unauthorized access.

Does this secrets audit work without needing additional dependencies or components?▼

This secrets audit operates without requiring additional dependencies or components. It runs directly on your codebase to identify exposed credentials and sensitive data using built-in pattern matching and heuristic analysis.