publish-code

Automate private repository preparation for open-source publication with license and documentation checks.

Updated Jan 10, 2026

Search Tags:#github #license #publish #contributing #open-source #repo-management

Ready to run

npx skills add https://github.com/jas-ho/jason-agent-skills --skill publish-code

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: publish-code
Source: https://github.com/jas-ho/jason-agent-skills/tree/main/plugins/publish-code
Command: npx skills add https://github.com/jas-ho/jason-agent-skills --skill publish-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers transition a private repository into an openly shareable project by automating license setup, documentation readiness, and public visibility.

Core Features & Use Cases

License provisioning and contributing guidelines generation to enable open-source licensing and clear collaboration.
Documentation polish and readiness checks (README quality, basic CONTRIBUTING, license mention) to reduce onboarding friction for external users.
Publication workflow from quick scan to public release, including optional announcements and GitHub visibility adjustments, with deterministic checks for safety and hygiene.

Quick Start

Run the publish-code workflow to prepare a private repository for open-source release, including license, README polish, and public visibility.

Frequently Asked Questions about publish-code

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

FAQPage Schema

How do I prepare a private GitHub repository for open-source publishing?▼

To prepare a private GitHub repository for open-source publishing, run a workflow that scans the project, provisions licenses, polishes README files, generates contributing guidelines, and adjusts visibility settings for public release.

What documentation do I need to publish an open-source project?▼

Publishing an open-source project requires a valid license, a polished README for user onboarding, and a CONTRIBUTING file to establish clear collaboration guidelines and project hygiene.

How can I automate license setup and contributing guidelines generation before making a repo public?▼

You can automate license setup and contributing guidelines generation by running a configurable workflow that performs deterministic checks for safety, provisions the required license, and generates the necessary documentation.

Does the open-source publishing workflow apply to any programming language?▼

Yes, the open-source publishing workflow applies to any repository type and programming language, guiding users from a quick scan to targeted fixes like CI hooks and license provisioning.

What is the best way to transition a private repo to public visibility safely?▼

The best way to transition a private repo to public visibility safely is to use a deterministic workflow that checks project hygiene, verifies license handling, ensures documentation quality, and confirms release readiness before flipping visibility.

When should I not use an automated workflow to publish code to GitHub?▼

You should not use an automated workflow to publish code if your repository requires custom legal licensing terms outside standard open-source provisions, or if manual review of sensitive data is needed before public visibility.