skills.rest
slbug
slbugCOMMUNITY
Explore all skills by this author →
GitHub

rb:secrets

Detect leaked secrets and exposed credentials in Ruby codebases.

7|Updated Mar 22, 2026
Search Tags:#security#secrets#credentials#pre-commit#git-history#secret-scan#betterleaks
One-click install
npx skills add https://github.com/slbug/claude-ruby-grape-rails --skill rb-secrets
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rb:secrets
Source: https://github.com/slbug/claude-ruby-grape-rails/tree/main/plugins/ruby-grape-rails/skills/secrets-scan
Command: npx skills add https://github.com/slbug/claude-ruby-grape-rails --skill rb-secrets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects accidental inclusion of secrets, API keys, and credentials in a codebase to prevent sensitive data from being committed or distributed.

Core Features & Use Cases

  • Repository scanning: Run pattern- and heuristic-based scans over project files and git history to find exposed keys, tokens, and private keys.
  • Baseline and validation: Support for baseline files to ignore known findings and an optional validation mode to verify high-confidence leaks against live APIs.
  • Use Case: Run this before committing or in CI to catch hardcoded credentials in Rails, Grape, or Ruby projects and receive remediation guidance such as adding files to .gitignore or rotating keys.

Quick Start

Run a secrets scan on the project root with a baseline file and include validation to produce a prioritized findings report and remediation steps.

Frequently Asked Questions about rb:secrets

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

FAQPage Schema
How do I scan my git history for leaked secrets and credentials?▼

Scanning git history for leaked secrets involves running pattern- and heuristic-based checks across your repository to identify exposed API keys, tokens, and private keys before they are distributed.

How do I prevent hardcoded credentials from being committed in a Rails project?▼

Preventing hardcoded credentials in Rails projects requires running pre-commit checks and repository scans to catch exposed keys, providing remediation guidance like updating .gitignore or rotating keys.

Does this secret scan tool require any specific dependencies or setup?▼

Yes, this secret scan requires installing betterleaks. It also supports baseline files to ignore known findings and an optional validation mode to verify high-confidence leaks against live APIs.

What is the best way to handle false positives when scanning code for exposed API keys?▼

The best way to handle false positives when scanning for exposed API keys is using baseline files to ignore known findings, alongside an optional validation mode to verify high-confidence leaks against live APIs.

Can I scan environment and configuration files for sensitive data exposure?▼

Yes, you can scan environment and configuration files for sensitive data exposure. The tool targets repositories and paths to detect secrets and exposed credentials across your codebase.

Does the pre-commit secret scan work with Grape and Ruby projects?▼

Yes, the pre-commit secret scan works with Rails, Grape, and Ruby projects, detecting accidental inclusions of secrets, API keys, and credentials to prevent sensitive data from being committed.

Related Skills

Explore More Software Engineering Skills→
GavinTPAGavinTPA

security-check

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

Community
Advanced
Greenmamba29Greenmamba29

env-secrets-auditor

Scan environment files and codebases for exposed secrets and generate a remediation report.

Community
Intermediate
slbugslbug
7

security

Enforce authorization, SQL injection, XSS, and secret security in Rails and Grape applications.

Community
Intermediate
patricio0312revpatricio0312rev
5

secrets-scanner

Detect leaked credentials in codebases across pre-commit hooks and CI pipelines.

Community
Advanced