skills.rest
yanochka11
yanochka11COMMUNITY
Explore all skills by this author →
GitHub

secret-guard

Detect secret patterns and validate git changes before commits and pushes.

Updated May 5, 2026
Search Tags:#git#security#github#secrets#credentials#api keys
One-click install
npx skills add https://github.com/yanochka11/harness_bro --skill secret-guard-yanochka11
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: secret-guard
Source: https://github.com/yanochka11/harness_bro/tree/main/.claude/skills/curated/secret-guard
Command: npx skills add https://github.com/yanochka11/harness_bro --skill secret-guard-yanochka11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents accidental exposure of API keys, tokens, passwords, and other sensitive credentials during software development workflows, helping keep repositories secure.

Core Features & Use Cases

  • Secret Detection Guidance: Identifies common credential patterns and blocks unsafe handling of keys, tokens, private keys, and connection strings.
  • Git Safety Checks: Provides procedures for reviewing changes before commits, pushes, and pull requests to avoid publishing secrets.
  • Secure Development Practices: Guides developers toward environment variables and secret stores instead of hardcoded credentials.

Quick Start

Ask the secret-guard skill to review my changes before committing them to GitHub.

Frequently Asked Questions about secret-guard

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

FAQPage Schema
How do I check for API keys and secrets before a git commit?▼

Checking for API keys and secrets before a git commit involves reviewing staged changes against common credential patterns. This blocks unsafe tokens, private keys, and connection strings from entering version control workflows.

What is the best way to prevent accidental secret leaks in GitHub?▼

Preventing accidental secret leaks in GitHub requires reviewing changes before commits, pushes, and pull requests. Validating secret patterns and using secure development practices like environment variables ensures credentials are not exposed in source code.

How do I scan source code for hardcoded credentials and environment files?▼

Scanning source code for hardcoded credentials requires secret pattern validation across files and staged changes. It identifies sensitive API keys and passwords, guiding developers toward secure environment variables and secret stores instead.

Does this git security check work for environment files and pull requests?▼

Yes, git security checks apply to environment files, commits, pushes, and pull requests. It validates secret patterns across development workflows to satisfy repository security checks and keep credentials protected during code reviews.

Why should I use environment variables instead of hardcoded credentials in git?▼

Using environment variables instead of hardcoded credentials in git prevents accidental exposure of sensitive data. Hardcoded API keys and tokens easily leak during commits or pushes, whereas environment variables keep secrets out of source code securely.

Related Skills

Explore More Software Engineering Skills→
zhangzhang-111-izhangzhang-111-i
2

env-secrets-manager

Scan repositories for environment variable and secret leaks.

Community
Intermediate
truefoundrytruefoundry
1

truefoundry-secrets

Manage TrueFoundry secret groups and key-value secrets via API and CLI.

Official
Advanced
jordanhubbardjordanhubbard
9

requesting-code-review

Automate pre-commit code review with static analysis and security scans.

Community
Advanced
jeremylongshorejeremylongshore
2.6k

building-cicd-pipelines

Generate CI/CD pipeline configurations for GitHub Actions, GitLab CI, and Jenkins.

Community
Intermediate