wip-repo-permissions-hook

To prevent accidental public exposure of internal GitHub repository context, this skill enforces a policy requiring a corresponding '-private' repository to exist before any repository can be made public, safeguarding internal development context.

To audit public repositories for compliance, use the provided CLI commands to check individual repositories and audit entire organizations, ensuring every public repository has a required '-private' counterpart.

Yes, you can integrate repository visibility checks as a hook into AI development platforms like Claude Code and OpenClaw. It automatically blocks making a repository public if the '-private' counterpart does not exist.

Yes, the tool exposes its repository visibility enforcement functionality via MCP, allowing programmatic access to check if a repository can be made public based on the '-private' counterpart rule.

If you try to make a GitHub repository public without a private counterpart, the visibility enforcement mechanism automatically blocks the attempt. This strict policy ensures internal development context is never accidentally exposed.

You need a '-private' repository before making a repo public to safeguard internal development context, such as internal notes, plans, and AI development artifacts. This separation prevents sensitive information from leaking into public repositories.