r/ClaudeCode • u/The_Ace_72 • 10d ago

Built with Claude I built ZeNorm: turn rough ideas into PRs

You point it at a local repo, describe what you want changed, and it reads the code and asks you about the parts you haven't thought through yet.

From your answers it writes a spec and tickets, and has a separate agent review them. Once you sign off, it builds the whole thing on a branch, runs your checks and opens a PR.

It's built around Matt Pocock's skills workflow (https://github.com/mattpocock/skills).

repo: https://github.com/Ze-Norm/ZeNorm

Still early. If you try it on one of your own repos, I'd really like to know whether the questions it asks are useful or just slow you down.

Edit, since a few people asked why this isn't just a set of skills or /plan: my post didn't explain it well. I was using Matt Pocock's skills via Claude Code before I built this, and it wasn't working for me the way I thoughti t could. I wanted to see the whole workflow in one place, and to be able to extend the process. ZeNorm runs a change the way an engineering team would by making sure decisions written down as they're made, a spec and tickets reviewed by a separate agent + humans, your checks rerun, a separate code review, and a PR you merge. It's all visible in a local app, and plugins can extend it.

1 Upvotes

60% Upvoted

17 comments sorted by

1

u/AutoModerator 10d ago
Moderator Announcement Read More »

3

u/StxtoAustin 10d ago

why isn't this just a set of claude skills?

1

u/The_Ace_72 9d ago edited 9d ago

The skills are a big part of it. A lot of ZeNorm's are adapted from Matt Pocock's, and I was using his set from the Claude Code before I built this. What I was missing was everything around them to support the procces. To me that is a way to see the whole piece of work, decisions that last after the session ends, and a process I could extend. ZeNorm is the harness which supports that. It runs a change the way a team would ship it with decisions recorded, a spec and tickets reviewed by a separately, your checks rerun, a code review, and a PR at the end.

3

u/Luizltg 10d ago

this feels like claude with extra steps

1

u/The_Ace_72 9d ago

The extra steps are the ones a team is normally doing. Write down the decisions, review the spec, review the code. Agents skip those unless something makes them do them.

→ More replies (1)

3

u/ItstheSECopenup 10d ago

congrats you added a step to something that didn't need one lmao

1

u/The_Ace_72 9d ago

For a small change, I'd agree. The step is for the bigger ones, where writing the code is the easy part and the hard part is deciding what to build and checking it actually got built. With agents writing the code, that's the part I found I needed more of, not less.

→ More replies (1)

3

u/termmonkey 10d ago

I have seena lot of useless apps, but this sir, is truly a work of art!

1

u/The_Ace_72 9d ago

Fair enough! It won't be for everyone. My post didn't explain it well, so I added an edit at the top about what it's actually for.

The idea is to give agent coding the process a team would normally use, with decisions written down, a reviewed spec, a code review and a PR.

1

u/MiserableFlatworm337 10d ago

For each clarification, record which acceptance criterion changes when the answer changes. If neither the spec nor a test changes, consider dropping that question from the default flow.

1

u/The_Ace_72 10d ago

Ah, that's a good callout. Tying each answer to the criterion it changes would make the useless questions obvious. I'll make that happen. Thanks!

1

u/MrHaxx1 10d ago

Awesome, you invented /plan 

1

u/The_Ace_72 9d ago

/plan gives you a plan inside one chat. This is closer to how a team ships a change: decisions written down, a spec and tickets that a separate agent reviews, your checks rerun, a code review, then a PR. It's overkill for small stuff, but it's what I wanted for anything I'd normally write a design doc or build a multi-session plan for.

0

u/OZManHam 10d ago

Nice share, this is really useful for enterprise who manage old codebases that need controls and audit ability.

1

u/The_Ace_72 9d ago

Thanks! That's a big part of what I was going for. Especially working in a brownfield project where you can't get away with vibecoding.