public-repo-ip-audit

Detect proprietary IP leakage in public repositories before commit or push.

8|1|Updated Jan 24, 2026

Search Tags:#compliance #pre-push #code-security #public-repo #ip-audit #pattern-registry

Ready to run

npx skills add https://github.com/bordenet/superpowers-plus --skill public-repo-ip-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: public-repo-ip-audit
Source: https://github.com/bordenet/superpowers-plus/tree/main/skills/security/public-repo-ip-audit
Command: npx skills add https://github.com/bordenet/superpowers-plus --skill public-repo-ip-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit public repositories for proprietary IP before commit/push. Prevents leakage of internal references, URLs, ticket IDs, and confidential content to public repositories regardless of hosting platform (GitHub, GitLab, Bitbucket, Codeberg, SourceHut, self-hosted, etc.).

Core Features & Use Cases

Mandatory gates (Working tree scan, Staged changes, Unpushed commits, Design/docs in PRIVATE repo) must pass before any push.
IP Pattern Registry and blocking conditions help prevent leakage of internal URLs, emails, and ticket references.
Build and apply pre-push checks across hosting platforms, with triage of matches and remediation guidance.

Quick Start

Run the IP audit before pushing to ensure no internal references are leaked.

Frequently Asked Questions about public-repo-ip-audit

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

FAQPage Schema

How do I prevent internal IP leakage in a public repository before a push?▼

To prevent IP leakage, an audit scans the working tree, staged changes, and unpushed commits to detect and block internal references, URLs, ticket IDs, and confidential content before they reach a public repository.

Does pre-push IP auditing work with self-hosted Git repositories and other hosting platforms?▼

Pre-push IP auditing works across any public repository regardless of the hosting platform, including GitHub, GitLab, Bitbucket, Codeberg, SourceHut, and self-hosted environments, by enforcing its checks locally.

How do I scan staged changes for confidential content and internal ticket references?▼

Scanning staged changes involves applying an IP pattern registry and blocking conditions through a multi-gate pre-commit workflow, which identifies internal URLs, emails, and ticket references to provide remediation guidance.

What is the best way to detect proprietary code references before pushing to a public repo?▼

The best way to detect proprietary code references is running a multi-gate workflow that scans the working tree, staged files, and unpushed commits, checking against an IP pattern registry to block leakage.

Why does my pre-commit workflow need multiple gates to block IP leakage?▼

A multi-gate pre-commit workflow is needed to thoroughly block IP leakage by separately scanning the working tree, staged changes, unpushed commits, and verifying design or docs remain in a private repository.

Are there limitations to using an IP pattern registry for detecting confidential content in code?▼

An IP pattern registry detects confidential content by matching defined internal URLs, emails, and ticket references, meaning it requires properly configured patterns to effectively block identified leakage vectors.