skills.rest
kevinslin
kevinslinCOMMUNITY
Explore all skills by this author →
Website𝕏@kevins8GitHub

dev.can-make-public

Scan repositories and git history for secrets and sensitive artifacts.

21|Updated Jan 3, 2026
Search Tags:#security#audit#secrets#credentials#open-source#git-history
One-click install
npx skills add https://github.com/kevinslin/skills --skill dev-can-make-public
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev.can-make-public
Source: https://github.com/kevinslin/skills/tree/main/active/dev.can-make-public
Command: npx skills add https://github.com/kevinslin/skills --skill dev-can-make-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and mitigate accidental exposure of secrets and sensitive data in codebases before making them public, reducing risk of data breaches and compliance issues.

Core Features & Use Cases

  • Filenames scan for common secret files (env, key files, credentials indicators).
  • Content scan for patterns like API keys, tokens, and private keys across working tree and history.
  • Use case: pre-publication audits for open-source releases or external sharing, with remediation guidance.

Quick Start

Provide the repository you want to audit and I will scan for secrets and sensitive data before public release.

Frequently Asked Questions about dev.can-make-public

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

FAQPage Schema
How do I scan a repository for secrets and credentials before open-sourcing?▼

Scanning a repository for secrets before open-sourcing involves checking filenames for sensitive artifacts and searching content patterns for API keys and tokens. This process identifies accidental exposure of sensitive data across the working tree and git history, guiding necessary remediation prior to public release.

What is the best way to audit git history for leaked API keys and tokens?▼

Auditing git history for leaked API keys requires optional historical analysis to trace sensitive artifacts and content patterns. This identifies credentials committed in previous iterations, providing remediation guidance to sanitize the repository before external sharing or open-source publication.

Can I check my codebase for sensitive files like env or key files before publication?▼

Yes, pre-publication audits scan filenames for common secret files such as env, key files, and credential indicators. This verifies that sensitive artifacts are detected and removed from your codebase before making the repository public, ensuring compliance and reducing breach risks.

Does this secrets audit work with any GitHub project or codebase?▼

This secrets audit is applicable to GitHub projects and other code bases during open-source preparation. It performs pre-publication audits and sanitization checks to ensure your repository is free of exposed credentials and sensitive artifacts before public release.

Related Skills

Explore More Software Engineering Skills→
mattbobambrosemattbobambrose
1

check-secrets

Detect committed secrets and sensitive files in git history and working tree.

Community
Intermediate
bianhaifeng789-huebianhaifeng789-hue

sanitize-git-repo

Detect and remove committed secrets from git repositories and history.

Community
Advanced
jeremylongshorejeremylongshore
2.6k

building-cicd-pipelines

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

Community
Intermediate
riandeoliveirariandeoliveira

implementing-secret-scanning-with-gitleaks

Scan Git repositories with Gitleaks to detect and prevent hardcoded credentials.

Community
Advanced