publish-repo

Automate repository publication to GitHub with security checks and cleanup.

26|2|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/sburl/CrossCheck --skill publish-repo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: publish-repo
Source: https://github.com/sburl/CrossCheck/tree/main/codex/skills/publish-repo
Command: npx skills add https://github.com/sburl/CrossCheck --skill publish-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the safe and compliant publishing of a repository to GitHub by auditing for secrets, trimming dead code, refreshing documentation, verifying licensing, and pushing to a public remote.

Core Features & Use Cases

  • Security Audit: Scans for hardcoded secrets, sensitive files, and license compliance issues before release.
  • Dead Code Cleanup: Removes unused files and cleans up project structure to reduce surface area.
  • Documentation & Licensing: Verifies README presence and license files, updating docs where needed.

Quick Start

Run the publish-repo skill on the repository you intend to release and follow the prompts to push to the public remote.

Frequently Asked Questions about publish-repo

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

FAQPage Schema
How do I publish a repository to GitHub while ensuring no secrets are exposed?▼

To publish a repository safely, you must run a security audit to scan for hardcoded secrets and sensitive files before pushing. This skill automates that process by scrubbing secrets, verifying licenses, and pushing to a public remote.

What is the best way to remove dead code before making a GitHub repository public?▼

Removing dead code before making a GitHub repository public involves cleaning up unused files to reduce the attack surface. This skill automates dead code cleanup as part of a deterministic release workflow before pushing to the public remote.

How do I automate repository release workflows with documentation and license verification?▼

Automating repository release workflows requires verifying README presence and license files alongside code cleanup. This skill enforces these documentation checks and license verification in a defined sequence before pushing to GitHub.

Does this repository cleanup process support auditability for security checks?▼

Yes, the repository cleanup process supports auditability by providing clear logs of the security review and code cleanup steps. It enforces deterministic steps to ensure a compliant and traceable release workflow before pushing.

Can I use this tool to refresh documentation and verify licensing before pushing to a public remote?▼

Yes, you can use this tool to refresh documentation and verify licensing before pushing to a public remote. It explicitly checks for README presence, updates docs where needed, and verifies license files as part of the publication sequence.