Berat

Solo builder on the side of a 9-5 job

📣 (12$)
🃏 (30$)
💤 (0%)

[Berat @beratbuilds]

TabRush is live! 🚀

I built a playful ad marketplace where one Safari tab becomes the spotlight for your product.

• One main tab for the latest sponsor
• Side tabs for previous sponsors
• Dynamic pricing that grows with each booking
• Fast, simple placement flow

No complex ad setup.
No crowded dashboards.

Just publish fast and get seen.

Try it now → https://t.co/8WWEuXz7t0

[Berat @beratbuilds]

Dependency bumps are not features.
CI fixes are not features.
Internal refactors are not features.

These are ~40% of most merged PRs. They all end up in the changelog anyway.

[Berat @beratbuilds]

The people who write the best PR titles are usually the ones who've had to write release notes before.

The fastest way to improve your team's PR quality is to make everyone write the release notes once.

[Berat @beratbuilds]

GitHub's auto-generated release notes are accurate and useless.

A list of PR titles tells engineers what changed.
It tells nobody else anything.

Accurate ≠ useful.

But ReleaseHub is different!

[Berat @beratbuilds]

When using an LLM for classification tasks, don't ask it to classify directly.

Ask it to reason first:
"What does this change mean for the end user?"
Then classify.

Hit rate went from ~70% to ~92% with that one change.

[Berat @beratbuilds]

@ScientificSaaS @marclou +1

[Berat @beratbuilds]

Hot take: most AI wrappers aren't products. They're features looking for an app.

The ones that survive are where the AI is doing something the user couldn't or wouldn't do manually.

[Berat @beratbuilds]

Most teams have a "release notes person."

It's usually whoever complained about the release notes being bad.

Ownership by complaint is a real pattern.

[Berat @beratbuilds]

Most teams have a "release notes person."

It's usually whoever complained about the release notes being bad.

Ownership by complaint is a real pattern.

So welcome to ReleaseHub!

[Berat @beratbuilds]

Tip: store CLI config in ~/.toolname/config.json, then immediately:

chmod 600 ~/.toolname/config.json

Without this, the file (and any API tokens in it) is world-readable on a shared machine.

One line. Easy to forget.

[Berat @beratbuilds]

I spent a week building GitHub OAuth before anyone could see what the tool actually does.

Device flow, token storage, secure config — all done.
Zero users had seen the output yet.
Should have started with a plain --token flag.
Auth isn't the product.

[Berat @beratbuilds]

Most teams have a "release notes person."

It's usually whoever complained about the release notes being bad.

Ownership by complaint is a real pattern.

So welcome to ReleaseHub!

[Berat @beratbuilds]

Tip: before npm publish, always run:

npm pack --dry-run

Shows exactly what files go into the package. Caught me including planning docs, test fixtures, and a .env example once.

[Berat @beratbuilds]

@buildinpublic ReleaseHub — open source CLI that reads your merged PRs and writes release notes for you. Anthropic, OpenAI, or Gemini. One command, three output formats.
https://t.co/h5fIyaqbFh

https://t.co/HKAY2ojVCz

[Berat @beratbuilds]

Just shipped ReleaseHub — open source CLI that turns GitHub PRs into release notes using AI.

• Fetches merged PRs between tags
• Classifies & rewrites with Claude or GPT-4o
• Outputs github-release, changelog, or slack format
• --publish creates the GitHub Release directly

[Berat @beratbuilds]

Most teams have a "release notes person."

It's usually whoever complained about the release notes being bad.

But now there's a better way, of course.

[Berat @beratbuilds]

"Fix token refresh race condition" means nothing to a user.
"You were getting logged out randomly — this is fixed" means everything.

Same change. Different vocabulary. Someone has to translate.
ReleaseHub already does this for you.

[Berat @beratbuilds]

"Fix token refresh race condition" means nothing to a user.
"You were getting logged out randomly — this is fixed" means everything.

Same change. Different vocabulary. Someone has to translate.
ReleaseHub already does this for you.

[Berat @beratbuilds]

@DoanDadelen5 ama, Biz bir takımız!

[Berat @beratbuilds]

Tip: when batching LLM requests, 20 items per call hits the sweet spot.

1 item/call → expensive and slow
100 items/call → context overflow, hard to parse

20 items → ~10x cheaper than 1/call, same accuracy, predictable output.

[Berat @beratbuilds]

Money isn't just about achievement; if you're working on an open-source project, every star is valuable and makes you feel good.

[Berat @beratbuilds]

Just shipped ReleaseHub — open source CLI that turns GitHub PRs into release notes using AI.

• Fetches merged PRs between tags
• Classifies & rewrites with Claude or GPT-4o
• Outputs github-release, changelog, or slack format
• --publish creates the GitHub Release directly

[Berat @beratbuilds]

What's your install-to-first-value time for tools you actually use daily?

The ones I keep using: under 2 minutes.
The ones I uninstall: "first, configure your..."

[Berat @beratbuilds]

Built a fully functional open source app in a few hours using vibe coding what used to take days now takes an afternoon.

The gap between idea and shipped product has never been smaller, and it's only getting wider.

[Berat @beratbuilds]

GitHub's auto-generated release notes are accurate and useless.

A list of PR titles tells engineers what changed.
It tells nobody else anything.

Accurate ≠ useful.

But ReleaseHub is different!

[Berat @beratbuilds]

GitHub's auto-generated release notes are accurate and useless.

A list of PR titles tells engineers what changed.
It tells nobody else anything.

Accurate ≠ useful.

But ReleaseHub is different!

[Berat @beratbuilds]

If your CLI's --help output doesn't fit in a terminal window, the command is doing too much.

One command, one job. Split the rest.