skills.rest
edfenton
edfentonCOMMUNITY
Explore all skills by this author →
Website𝕏@edfentonGitHub

github-visibility

Toggle a GitHub repository between private and public states.

3|1|Updated Feb 12, 2026
Search Tags:#automation#security#github#visibility#preflight#codeql#branch-protection
One-click install
npx skills add https://github.com/edfenton/claude-skills --skill github-visibility
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-visibility
Source: https://github.com/edfenton/claude-skills/tree/main/shared/github-visibility
Command: npx skills add https://github.com/edfenton/claude-skills --skill github-visibility

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Safely toggle a GitHub repository between private and public visibility while applying appropriate security and access settings.

Core Features & Use Cases

  • Pre-flight safety checks before making a repo public to prevent accidental exposure.
  • Adjusts repository features (issues, wiki, discussions, projects) and enables CodeQL/security settings when public.
  • Works alongside /github-secure to patch CodeQL conditions and update branch protections as part of the workflow.

Quick Start

Switch the current repository to the desired visibility (public or private) by specifying the explicit target and an optional --force flag.

Frequently Asked Questions about github-visibility

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

FAQPage Schema
How do I safely change a GitHub repository from private to public?▼

To safely change GitHub repository visibility from private to public, you need pre-flight safety checks to prevent accidental exposure and automatic adjustments to repository features, CodeQL conditions, and branch protections.

What security settings need updating when making a GitHub repo public?▼

When making a GitHub repo public, security settings must update by patching CodeQL conditions in security.yml and updating branch protections to enforce access hardening and prevent unauthorized changes.

Can I automate closing external pull requests when toggling repo visibility?▼

Yes, when toggling GitHub repo visibility you can automate closing external pull requests by creating or removing the close-external-prs workflow as part of the repository lifecycle hardening process.

Does making a GitHub repository public require adjusting issues, wiki, and discussions?▼

Yes, changing GitHub repository visibility to public requires adjusting repository features including issues, wiki, discussions, and projects to align with the new public exposure and security posture.

What's the best way to enforce branch protection before opening a GitHub repository to the public?▼

The best way to enforce branch protection before opening a GitHub repository to public is to run a preflight workflow that patches CodeQL settings and updates branch protections alongside the visibility toggle.

Why do I need preflight checks before switching my GitHub repo to public visibility?▼

Preflight checks are needed before switching GitHub repo visibility to public to prevent accidental exposure of sensitive data and to ensure CodeQL security settings and branch protections are properly configured.

Related Skills

Explore More Software Engineering Skills→
L3DigitalNetL3DigitalNet
6

security

Audit GitHub repository security via Dependabot, code scanning, and branch protection.

Official
Advanced
balsm-healthbalsm-health
2

analyzing-kubernetes-audit-logs

Detect security threats in Kubernetes audit logs by parsing JSON lines.

Official
Advanced
duanbiao2000duanbiao2000
3

sast-configuration

Configure Semgrep, SonarQube, and CodeQL for automated vulnerability detection.

Community
Advanced
stark-ai-destark-ai-de
4

security-baseline-review

Review public repositories for security hygiene using git and the GitHub API.

Official
Intermediate