v2.0.0 β π Self-contained, and it only builds what it can prove
π The self-contained build OS
This is the big one β and it's built for first-timers, not just developers. π± You don't need to know how to code, and you don't learn a CLI: you enter Builder Mode, and it picks the right approach for where you are. Clone it, type one sentence in plain English, and it builds. Never used a terminal? There's a "Start here" on-ramp that walks you from zero β no coding required, you just talk to an AI and it does the techie parts.
And as of v2.0 the whole engine ships in the repo, so a fresh clone is complete. π οΈ
git clone https://github.com/hamza-ali-shahjahan/hamzaish
# open in Claude Code, then type:
/builder-mode <your idea>
(It routes on context and asks when it's unsure β gates, not guesswork.)
β¨ Highlights
- π± Built for beginners too. No dev experience needed β a "Start here" on-ramp takes a total first-timer from zero to building. You talk; it does the techie parts.
- πͺ One front door, it routes.
/builder-mode(or/hamzaish, or plain English) reads what you're building and where you are, then drives the right path β a quick change, the gated full cycle, or an autonomous self-verifying loop toward a goal. The ~65 skills & commands are the gears; you never drive them by hand. - π― Goal-first, eval-gated β it only builds what it can prove. The cycle pins what "done" means, slices the goal into features, and keeps only the ones it can prove β each ships with an eval and an end-to-end test. A feature it can't evaluate or test doesn't get built. "Done" is a green eval, not an opinion.
- π¦ The whole engine ships in the repo. spec β plan β build β test β review β ship, plus autonomous modes β 22 engineering skills + 3 subagents. No separate install; the clone is the whole thing.
- π Honest by force. 35 agents Β· 41 skills Β· 24 commands Β· 41 playbooks Β· 133 practices β and a CI guard derives every count from the filesystem and fails the build if a doc drifts, a path leaks, or the version disagrees across files. The counts are the filesystem, not the marketing.
π’ New & improved: real versioning (why this is v2.0, not v1.33)
Hamzaish now follows semver with a documented policy (docs/versioning.md), and a CI guard keeps the number honest across the whole repo (it used to read four different ways π
β never again):
- MAJOR = a milestone or a change in how you use it β v2.0 = the self-contained build OS. π―
- MINOR = a new capability Β· PATCH = a fix.
- Frequent changelog entries roll up into deliberate releases β no more drift.
So the jump from v1.2 β v2.0 is on purpose: this is a milestone, not an increment. π
π¦ What's changed since v1.2
- π§© The engineering engine (
/full-cycle,/auto,/goal,/spec,/plan,/build,/test,/reviewβ¦) consolidated into the repo β the front door is now self-contained on a fresh clone. - π― Goal β Slice β eval-gated build flow + the new
feature-slicingskill;/goalself-verifying loop shipped in-repo. - π The count / path / version CI guard β believability, mechanized.
- πΌοΈ Rebuilt Builder Mode banner + the versioning policy & drift guard above.
Full log β the changelog.
Works with Claude Code, Cursor, Codex & Windsurf Β· π AGPL-3.0 Β· needs a paid Claude plan (no free tier).
Built on Claude Code and a lot of generous open source. π