skills.rest
BSchafer01
BSchafer01COMMUNITY
Explore all skills by this author →
GitHub

github-publish-readiness-check

Audit a local repository for blockers before publishing to GitHub.

Updated Mar 16, 2026
Search Tags:#git#github#validation#repository#publish#preflight
One-click install
npx skills add https://github.com/BSchafer01/PanelNester --skill github-publish-readiness-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-publish-readiness-check
Source: https://github.com/BSchafer01/PanelNester/tree/main/.squad/skills/github-publish-readiness-check
Command: npx skills add https://github.com/BSchafer01/PanelNester --skill github-publish-readiness-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits a local repository to determine if it is ready to be published as a public GitHub remote, surfacing local-only state, build artifacts, and incomplete history that could impact the public release.

Core Features & Use Cases

  • Check git status, branches, and working-tree cleanliness to identify publish blockers
  • Verify gh CLI presence and authentication and validate access to create the remote
  • Validate target repository name availability on GitHub and prevent name conflicts
  • Enforce hygiene by ignoring common local-only directories and files to reduce noise
  • Report actionable blockers and recommended remediation steps for decision-making

Quick Start

Run the readiness audit on your current local repository to determine publish readiness.

Frequently Asked Questions about github-publish-readiness-check

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

FAQPage Schema
How do I check if my local git repository is ready to publish on GitHub?▼

Validate repository readiness by auditing git status, branch history, and working-tree cleanliness. A readiness check identifies local-only state, build artifacts, and incomplete history that could impact a public GitHub release.

What should I clean up before making a public GitHub repository?▼

Before making a public GitHub repository, enforce hygiene by ignoring local-only directories and files to reduce noise. You should also scan for secrets or large binaries and remove them from the working tree.

Do I need the gh CLI installed to validate my repository for publishing?▼

Yes, validating repository readiness requires the gh CLI to verify authentication and access to create the remote. The readiness check uses gh CLI to confirm target repository name availability on GitHub and prevent naming conflicts.

Can I check if a GitHub repository name is available before pushing my code?▼

You can check GitHub repository name availability before pushing by validating the target name against your authenticated GitHub account. The readiness audit uses gh CLI to confirm name availability and prevent remote creation conflicts.

Why does my preflight GitHub publish check flag untracked files?▼

A preflight GitHub publish check flags untracked files because local IDE state and build artifacts create noise in a public remote. The audit enforces hygiene by identifying these local-only files and recommending they be ignored before release.

Related Skills

Explore More Software Engineering Skills→
pekralpekral

production-audit

Analyze git history, configuration, and CI status to score PHP/Laravel production readiness.

Community
Advanced
kasperjungekasperjunge
450

make-release

Automate PyPI releases via GitHub Actions with version bumps and changelog updates.

Community
Advanced
piotrbpiotrb

validate-secrets

Detect unencrypted secret files in staged Git changes and block commits.

Community
Basic
open-haxopen-hax
6

git-safety-check

Check git branch, working tree, remotes, and submodules before destructive operations.

Official
Intermediate