skills.rest
GavinTPA
GavinTPACOMMUNITY
Explore all skills by this author →
GitHub

security-check

Detect hardcoded secrets and back up critical configuration files before edits.

Updated Apr 10, 2026
Search Tags:#git#security#audit#config#backup#secrets#pre-commit
One-click install
npx skills add https://github.com/GavinTPA/ai-powerhouse-starter --skill security-check-gavintpa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-check
Source: https://github.com/GavinTPA/ai-powerhouse-starter/tree/main/my-skills/security-check
Command: npx skills add https://github.com/GavinTPA/ai-powerhouse-starter --skill security-check-gavintpa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Prevents accidental destruction of critical configuration files and the inclusion of hardcoded secrets in tracked settings by creating backups, scanning for sensitive tokens, and blocking risky commits before changes are applied.

Core Features & Use Cases

  • Pre-edit backups: Automatically create timestamped backups of critical files (for example ~/.zshrc) before any edit to enable recovery from destructive edits.
  • Secret detection & settings audit: Scan .claude/settings.local.json and repository files for API keys, tokens, base64 blobs, and hygiene issues, reporting findings without exposing full secrets.
  • Environment health & git history scan: Verify required environment variables are present and scan git history for leaked credentials; install a pre-commit hook to block new secrets from entering history.
  • Use case: Run a full audit before open-sourcing a project to find committed API keys and install the pre-commit hook to prevent future leaks.

Quick Start

Use the security-check skill to run a full audit of your settings and scan the repository for secrets.

Frequently Asked Questions about security-check

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

FAQPage Schema
How do I scan git history for leaked secrets and API keys?▼

To scan git history for leaked secrets, run a full audit using pattern-based detection scripts that identify committed API keys, tokens, and base64 blobs without exposing the full secret values.

How do I prevent hardcoded secrets from entering my git pre-commit hook?▼

Prevent hardcoded secrets by installing a pre-commit hook that blocks risky commits before changes are applied, verifying environment variables and scanning settings files for sensitive tokens.

What is the best way to backup shell configs before an edit?▼

The best way to backup shell configs is creating timestamped backups of critical files like ~/.zshrc before any edit, enabling quick recovery from destructive changes to your environment settings.

Does secret detection work for local development settings like .claude configurations?▼

Secret detection works for local development by scanning .claude/settings.local.json and repository files for API keys, tokens, base64 blobs, and hygiene issues, reporting findings without exposing full secrets.

How do I audit environment variables and repository files before open-sourcing a project?▼

Audit environment variables and repository files by running a full security check that verifies required environment variables are present and scans settings for hardcoded tokens before open-sourcing your project.

Related Skills

Explore More Software Engineering Skills→
richfremrichfrem
5

hf-init

Validate HuggingFace environment variables and create a structured dataset repository on the Hub.

Community
Advanced
drvossdrvoss
42

secret-detection

Detect hardcoded API keys, tokens, and passwords in source code and git history.

Community
Intermediate
JackSmack1971JackSmack1971

git-commit-standards

Configure pre-commit hooks to validate conventional commit messages.

Community
Intermediate
kvithayathilkvithayathil

security-scan

Scan codebases with 17 SAST engines and generate Markdown reports.

Community
Intermediate