chrilleweb

I’ve been working on a small open source CLI tool in my spare time and recently reached a point where it feels “done enough” to share — but I’m unsure what the right next steps are.

So far I’ve tried: - Writing a clear README with examples - Adding documentation and usage guides on my docs website - Sharing it in one or two relevant discussions (without spamming)

I’m explicitly not trying to market it aggressively — I’d rather get it in front of the right people and receive honest feedback.

For those of you who’ve shipped open source projects that actually got adopted: What made the biggest difference early on? What do you wish you had done sooner?

If it helps, the project it's the link if you have any tips

Thanks!

I recently built a small open source CLI tool that scans a codebase for environment variable issues (missing env vars, unused vars, framework-specific mistakes like Next.js / t3-env, etc.).

I’m not trying to grow users yet — I’m mainly looking for honest technical feedback: - Is the problem real? - Are there obvious flaws in the approach? - Could this be used in your workflow?

For people who’ve shipped OSS tools before: What worked best for you when gathering early feedback from experienced developers?

Thanks!