repomix-safe-mixer

Scan codebases for hardcoded credentials and block repomix packaging when detected.

1.3k|212|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/daymade/claude-code-skills --skill repomix-safe-mixer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repomix-safe-mixer
Source: https://github.com/daymade/claude-code-skills/tree/main/repomix-safe-mixer
Command: npx skills add https://github.com/daymade/claude-code-skills --skill repomix-safe-mixer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires repomix, python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents accidental exposure of hardcoded credentials when packaging codebases with repomix, ensuring secure distribution and reducing security risks.

Core Features & Use Cases

  • Automated Secret Scanning: Scans directories for common hardcoded credentials (API keys, tokens, database secrets).
  • Safe Packaging: Blocks repomix packaging if secrets are detected, prompting remediation.
  • Use Case: Before sharing a project with a client or open-sourcing a tool, use this skill to automatically scan and ensure no sensitive API keys or database credentials are accidentally included.

Quick Start

Use the repomix-safe-mixer skill to safely package the project in './my-web-app' into a repomix XML file.

Frequently Asked Questions about repomix-safe-mixer

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

FAQPage Schema
How do I prevent hardcoded credentials from leaking when packaging code with repomix?

Hardcoded credentials leak when packaging code without scanning first. This Skill scans directories for API keys, tokens, and database secrets before running repomix, blocks packaging if secrets are found, and reports exact file and line locations so you can remove them safely.

Can I automate secret detection before sharing or open-sourcing a project?

Yes. This Skill automatically scans for common credential patterns in your codebase, produces a detailed report with file and line numbers, and prevents repomix packaging until all secrets are remediated, enforcing a clean-pack workflow.

What types of secrets does the scanning catch?

The Skill identifies common hardcoded credentials including API keys, authentication tokens, database connection strings, and other sensitive secrets that could expose your infrastructure or third-party integrations if packaged.

Does this work with existing repomix workflows?

Yes. The Skill integrates with repomix by scanning before packaging. It uses Python to scan for secret patterns, blocks repomix if threats are detected, and lets packaging proceed only when the scan is clean.

What happens if secrets are detected during a package scan?

The Skill stops the repomix packaging process, generates a report showing the file path and line number of each detected secret, and prompts you to remove the credentials before retrying the package operation.

Can I use this for security audits of existing codebases?

Yes. Beyond packaging workflows, the Skill scans any directory for hardcoded credentials and produces detailed findings with locations, making it useful for security-focused audits and credential remediation before code sharing or distribution.