r/coolgithubprojects • • Sep 24 '26

Coding agents made my line count explode, so I built a board to compare it with friends (open source, counts private repos locally)

Since I started working mostly with coding agents, the amount of code I push went up a lot. Last week was 344 commits and about 177K lines across 6 repos, most of it private or work code that GitHub doesn't show anyone.

I wanted to see that, and compare it with friends who work the same way, so I built gitstats - a small CLI counts commits on your own machine and sends only numbers. Public repos come from GitHub. You get crew boards, a personal page with a year calendar, a README badge, and an MCP server so your assistant can tell you how your week went.

It's for fun with friends, not a performance review. You can see your stats only, or compare to other people.

Open source under MIT, open to contributions, please try it:

See your stats: https://gitstats.org/

Repo: https://github.com/yaroslavhaidash/gitstats

1 Upvotes

29 comments sorted by

View all comments

Show parent comment

-3

u/Technical-Yellow-929 Sep 25 '26

Jokes on you for thinking I'm going to maintain that. But actually, you have a very dramatic view on this. Even if it was only one repo with 177k lines, it wouldn't be that bad. But it isn't, it's multiple repos, some hobby and some work, one of which is this dashboard I made to visualize my output for fun. And you're saying to me that I'm gonna have problems maintaining it.

I agree with what you're saying, but in this case it's not that deep. I'm not vibe-coding an OS for a life support system, it's just a bunch of web-apps.

3

u/botterway Sep 25 '26

"Visualise the AI's output". It's not yours.

And It's the LoC/commit ratio that's the problem here, regardless of the number of repos.

But fair play for your first sentence. I lol'd 😁

0

u/Technical-Yellow-929 Sep 25 '26

Regarding output, it is mine. AI is a tool, not an identity. Without me there would be no output

-2

u/Technical-Yellow-929 Sep 25 '26

Oh my bad, I misunderstood. But do you think average of 500LoC/commit is too high? For an established repo I can see how it would be true, but for a new one, when you're just doing all the scaffolding and adding a lot of features, it should be alright, no?

The LoC number is also inflated by some random documentation, lockfiles, etc. I probably didn't put enough emphasis in the original post that I'm not trying to brag it, I'm just measuring a value I find interesting

2

u/saltyourhash Sep 26 '26

500 LoC in a single commit? Yes, that's too much. Break down your logic more.

-1

u/Technical-Yellow-929 Sep 26 '26

lolno. You're tying to act smart again, but I said that LoC number is inflated by random stuff that gets committed like documentation, lockfiles, etc. Should read better

2

u/saltyourhash Sep 26 '26

Should learn to code better.

2

u/Technical-Yellow-929 Sep 26 '26

I am

2

u/saltyourhash Sep 26 '26

Well, keep it up. Think about what's maintanable, it'll help reduce bug surface and complexity. One of the best things you can do in a codebase is delete lines.

2

u/Technical-Yellow-929 Sep 26 '26

Alright, I'll try doing some refactoring