secret-handling

Scan staged files for credentials and block commits containing secrets.

1|Updated Dec 23, 2025

Search Tags:#automation #git #security #compliance #secrets #pre-commit

Ready to run

npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill secret-handling-jonnymuir

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: secret-handling
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.copilot/skills/secret-handling
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill secret-handling-jonnymuir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the accidental exposure of sensitive credentials and API keys by blocking the commit of files containing secrets to the repository history.

Core Features & Use Cases

Proactive Scanning: Automatically scans staged files for patterns matching API keys, passwords, and connection strings before any commit is finalized.
Safe Configuration Guidance: Enforces the use of safe templates like .env.example instead of reading live production environment files.
Incident Response: Provides clear, immediate instructions for remediation if a secret is detected in the git history.

Quick Start

Ask the agent to validate the current staging area for potential secret leaks before committing your changes.

Frequently Asked Questions about secret-handling

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

FAQPage Schema

How do I prevent secrets from being committed to git by automated agents?▼

To prevent secrets from being committed to git, you can use pre-commit hooks with regex-based pattern matching to automatically scan staged files for API keys and credentials before finalizing the commit.

What is a pre-commit hook for detecting sensitive credentials in version control?▼

A pre-commit hook for secret detection is a git integration mechanism that intercepts staged files and applies regex pattern matching to identify API keys, passwords, and connection strings before they enter repository history.

How do I scan staged files for environment variables before committing changes?▼

You scan staged files for environment variables by asking the agent to validate the current staging area, which checks for patterns matching sensitive configuration and enforces using safe templates like .env.example instead.

What should I do if a secret or API key is detected in git history?▼

If a secret or API key is detected in git history, you should follow immediate incident response instructions for remediation, which involves removing the credential from the repository history to secure your configuration.

Does pre-commit secret scanning work with automated agent workflows?▼

Pre-commit secret scanning works with automated agent workflows by integrating git hooks into file system operations and repository management, ensuring secure configuration handling during automated commits.