alexzhu0 Repo Launch Readiness Review
Purpose
Check whether a small repository is understandable, usable, and safe to publish.
Fit
- Use when a repo is close to public release and needs a final trust/readiness review.
- Do not use when the repo still lacks a working artifact or the task is deep implementation.
Inputs
- Repository README, file tree, metadata, examples, license, and release notes.
- Target audience, launch channel, and install path if available.
- Known validation commands and open issues.
Workflow
- Review whether a new visitor can understand the repo in under one minute.
- Check install, quickstart, examples, license, security, and contribution paths.
- Identify missing trust signals and confusing claims.
- Score readiness and list launch blockers separately from polish.
- Recommend the smallest changes before publishing.
Output
Produce Markdown with:
- Readiness Score
- Visitor Summary
- Launch Blockers
- Trust And Metadata Checks
- Example Quality
- Polish Tasks
- Recommendation
Validation
- Score rationale is visible.
- Blockers are separated from nice-to-have tasks.
- Claims in README are checked against files.
- Missing license or unsafe instructions are treated as blockers.
- Recommendations are small and release-oriented.