All skills
Release Readiness
GH Ready
Prepare repositories for professional GitHub publication, open-source release, NPM or package distribution, client delivery, hiring showcase, product launch, or handoff. Use when Codex needs to improve README quality, license readiness, package metadata, repository hygiene, community health files, issue and pull request templates, CI, tests, linting, release process, security policy, Dependabot, CodeQL/code scanning, secret hygiene, branch protection guidance, CODEOWNERS, changelogs, badges, docs, examples, AGENTS.md, or overall repository trustworthiness.
What this skill adds
This skill helps Codex make a repository look trustworthy, maintained, safe, and easy to use.
Required Reference
- Read references/gh-ready.md before making substantial repo changes. For a small README-only request, use the quick workflow and load the reference if scope expands.
Quick Workflow
- Inspect the repo root, README, license, package files, tests, CI, .github/, docs, examples, and Git status.
- Determine the audience: open source users, contributors, recruiters, enterprise buyers, internal handoff, or package consumers.
- Audit professional signals:
- - clear identity and README
- - install/use examples
- - license and attribution
Repo Upgrade Principles
- A professional repo explains what it is, why it exists, how to run it, how to trust it, and how to contribute.
- The README is a product surface, not a dumping ground.
- CI must verify the commands that the README tells users to run.
- Security policy, secret scanning, dependency updates, and branch protections matter as much as presentation.
- Public readiness includes removing private traces, old branding, analytics secrets, generated junk, and confusing dead files.
- Never remove license or attribution text casually.
Common Deliverables
- README.md
- LICENSE
- CONTRIBUTING.md
- CODE_OF_CONDUCT.md
- SECURITY.md
- SUPPORT.md
Default agent prompt
Use $gh-ready to make this repository professional, trustworthy, and release-ready.