We're adopting contribute-now as our open source workflow 🚀

[warengonzaga]

Hey Tiny Claw community! 👋

Wanted to share something exciting — going forward, we'll be using contribute-now as the official open source workflow for Tiny Claw. But first, let me share the "why" behind this decision.

The real problem in open source today

If you've contributed to popular open source projects, especially ones powered by AI agent frameworks, you've probably experienced this: you spend time writing a PR, only to have it closed with little to no explanation. Or you open an issue and it gets auto-triaged into oblivion. Many growing projects get flooded with PRs and issues to the point where managing contributions becomes the problem itself. Maintainers end up building automation just to handle the volume — auto-closing PRs, bot-driven triage, bulk issue management — instead of focusing on actually building the project.
But here's what I've realized: most of that chaos is a symptom, not the root cause. The real issue is that contributors often don't have clear guidance on how to contribute properly in the first place. They push to the wrong branch. They have merge conflicts because they're not synced with upstream. They follow the wrong commit conventions — or none at all. And when these things pile up across hundreds of contributors, it becomes unmanageable. So projects resort to closing everything and hoping automation will sort it out.
That's a terrible experience for contributors, and it's not sustainable for maintainers either.

Solving it at the local level

I've been on the contributor side of this problem, and it's frustrating. You want to help, you put in the work, but the system isn't set up for you to succeed. That experience is exactly why I built contribute-now — a CLI tool that guides contributors through the entire Git workflow before anything ever reaches the remote repo.

Instead of waiting for problems to show up as bad PRs and then automating them away, contribute-now gates the process at the local level. It makes sure contributors are synced, on the right branch, following the right conventions, and submitting clean work — all before they push. Think of it as building the foundation of proper contribution rather than patching the cracks after the fact.

What it does

contribute-now handles branching, syncing, committing, and PR submission with built-in guardrails. It supports multiple branching models (Clean Flow, GitHub Flow, Git Flow), enforces commit conventions, and even offers optional AI-powered assistance via GitHub Copilot for branch naming and commit messages. The goal is simple — let contributors focus on shipping quality work, not on memorizing git commands or guessing project conventions.

What this means for Tiny Claw

We don't want contributors to feel confused or frustrated when they try to help out. We want every contribution to be a smooth experience from start to finish. By adopting contribute-now, we're making sure that everyone who contributes to Tiny Claw has the guidance they need right from their local environment — so PRs land clean, conflicts are avoided, and no one's work gets thrown away because of process issues.

Get involved

This is a community effort and we'd love your input on how we can make contributing even better.

• Check out the project → github.com/warengonzaga/contribute-now
• Try it out → npx contribute-now
• Share your thoughts right here in this thread!

Let's build something great together, and make sure everyone who wants to contribute actually can. We build together like ants, one piece at a time, the ant way. 🐜