The problem I wanted to solve is pretty boring but real: before making a repo public or posting it somewhere, I always forget some public-facing detail. Not code quality exactly. More like:
- Is the README clear to a stranger?
- Is the first-run path obvious?
- Is there proof, demo output, or an example?
- Are license, security, contributing, and release notes in place?
- Is repo metadata filled out?
- Is the launch copy different for GitHub, Show HN, Reddit, etc.?
- Are there private notes, placeholders, or local paths that should not ship? So I packaged that into a Markdown skill Claude Code can follow. It audits the repo and returns a launch-readiness verdict split into code blockers, account/platform blockers, and launch blockers. Repo: https://github.com/OMARVII/open-source-launch-skill I’d appreciate any feedback on how to make it more useful. submitted by /u/OmarVII7
Originally posted by u/OmarVII7 on r/ClaudeCode
You must log in or # to comment.