Forge report · Launch-ready

gh-launchsmith

Tempered and ready to ship. LaunchSmith scored the repository from inspectable files and GitHub metadata; every recommendation below carries a receipt.

Positioning100

20/20 points

Proof100

20/20 points

Onboarding100

20/20 points

Trust100

20/20 points

Distribution100

20/20 points

GitHub metadata included · 0 star(s) · 10 topic(s)47 repository files inspected

Positioning

100/100

0 unresolved finding(s)

Forged

README exists

4/4

README.md

Next strike: Add a root README.md with a clear product title and promise.

Forged

Repository has a concise description

4/4

Evidence-first launch readiness for GitHub repositories — audit, prove, and package your open-source launch.

Next strike: Write a 50–140 character description stating the audience and outcome.

Forged

README opens with a concrete promise

4/4

Launch your GitHub repo like a product — with proof, not hype.

Next strike: Place one concrete outcome sentence directly below the title.

Forged

Audience or use cases are explicit

4/4

README contains a why/use-cases section.

Next strike: Add a short Why/Use cases section naming who should use the project.

Forged

GitHub topics support discovery

4/4

10 topic(s): agent-skill, developer-tools, github-actions, github-cli, launch, nodejs, open-source, oss, readme, repository-audit

Next strike: Add 5–10 precise GitHub topics covering category, language, and audience.

Proof

100/100

0 unresolved finding(s)

Forged

README shows the product

5/5

6 README image(s), 0 video link(s), 4 visual asset(s).

Next strike: Add a real screenshot, GIF, terminal capture, or short video near the top.

Forged

A runnable command is visible

4/4

12 fenced code block(s) include a runnable tool command.

Next strike: Add a copy-paste quick-start command and show what it does.

Forged

Tests or verification evidence exist

4/4

2 test file(s), 2 workflow(s).

Next strike: Add a repeatable test command and run it in CI.

Forged

A public release is available

4/4

v0.1.0 published 2026-08-11T03:40:40Z

Next strike: Publish a tagged first release with concise notes and install instructions.

Forged

Expected output is explained

3/3

README describes expected output.

Next strike: Show the output users should expect after the quick start.

Onboarding

100/100

0 unresolved finding(s)

Forged

Installation is easy to find

4/4

Install/setup heading detected.

Next strike: Add an Installation section before deep technical details.

Forged

Quick start is explicit

4/4

Quick-start heading detected.

Next strike: Add a Quick start that reaches the first useful result in under a minute.

Forged

Usage examples are present

4/4

12 code block(s); usage/example heading: yes.

Next strike: Add one realistic input → command → output example.

Forged

Prerequisites are documented

3/3

No clear prerequisites detected.

Next strike: State required runtimes, accounts, permissions, and supported platforms.

Forged

README has enough substance

3/3

6992 README character(s).

Next strike: Explain the problem, first result, core capabilities, and limitations without padding.

Forged

Failure recovery is documented

2/2

Troubleshooting/FAQ heading detected.

Next strike: Document the two or three most likely setup failures.

Trust

100/100

0 unresolved finding(s)

Forged

License is explicit

5/5

License file found.

Next strike: Add a LICENSE file before asking others to use or contribute.

Forged

Continuous integration is configured

4/4

2 GitHub Actions workflow(s).

Next strike: Run the primary test/lint command on pull requests.

Forged

Security reporting path exists

3/3

SECURITY file found.

Next strike: Add SECURITY.md with supported versions and a private reporting path.

Forged

Contribution path exists

3/3

CONTRIBUTING file found.

Next strike: Add a concise CONTRIBUTING.md with setup, tests, and PR expectations.

Forged

Change history is discoverable

3/3

Changelog/history file found.

Next strike: Use GitHub Releases or maintain a concise changelog.

Forged

Community expectations are stated

2/2

Code of conduct found.

Next strike: Add a standard code of conduct if community contributions are invited.

Distribution

100/100

0 unresolved finding(s)

Forged

A social-preview asset exists

4/4

Dedicated hero/social-preview asset found.

Next strike: Create a 1280×640 social preview with the product promise and real UI.

Forged

Launch materials are prepared

4/4

Launch pack detected.

Next strike: Run `gh launchsmith pack` and review every generated claim.

Forged

A demo or homepage is linked

3/3

https://lwu0rup.github.io/gh-launchsmith/

Next strike: Link a demo, documentation site, or hosted report in the GitHub homepage field.

Forged

Issue intake is prepared

3/3

Issue templates: yes; PR template: yes.

Next strike: Add focused bug/feature issue forms and a lightweight PR template.

Forged

README communicates project status

3/3

8 badge reference(s).

Next strike: Use a few meaningful badges for CI, release, license, and install path.

Forged

Release and discovery metadata align

3/3

Release: yes; topics: 10.

Next strike: Publish the first release and add focused discovery topics before launch day.