Community has been cooking this week 🚀
New contributors added support for @kilocode and @Kimi_Moonshot as well as porting the AI-blame extension to the @jetbrains ecosystem.
English
Git AI
11 posts
Git AI
@usegitai
the open standard for tracking AI-generated code
Git Repos شامل ہوئے Aralık 2025
2 فالونگ84 فالوورز
Git AI ری ٹویٹ کیا
Seeing this trend a lot of this across teams that use Git AI: enterprises are investing in their own background agents. I was skeptical at first, but I get it now.
Building and optimizing the factory will be the work of platform teams for the next 5 years.
Praveen Neppalli@praveenTweets
Agentic software engineering adoption is on fire at @Uber. 1,800 code changes per week are now written entirely by Uber's internal background coding agent, and 95% of our engineers now use AI every month across all the tools we track. This is a real reset moment for engineering; it's one of the most exciting times to lead. This shift requires builders to be curious and hands-on. I’m incredibly lucky to be surrounded by a team that’s doing exactly that. The best part is that the strongest adoption isn’t being pushed top down from leadership announcements; it’s coming from engineers who are quietly experimenting, quietly shipping, and quietly pushing things forward. I love spending time with those engineers because there’s no substitute for being close to the work. Over the last few months, we leaned in hard, and the results have been phenomenal. The bigger shift: going agentic. 84% of AI users are now working with agent-style workflows, not just tab completion. Claude Code usage nearly doubled in 2 months (32% → 63%), while IDE-based tools have largely plateaued. Engineers are moving from accepting suggestions to delegating tasks. Even within traditional IDEs, ~70% of committed code is now AI-generated. Background agents are writing code autonomously. Our internal background coding agent went from <1% of all code changes to 8% in just a few months. There is zero human authoring. Engineers review and approve, but the code is written entirely by AI agents. The role of the engineer is shifting - from writing every line to architecting systems and reviewing AI-generated code. More to come from the @UberEng team in the coming days.
English
Git AI ری ٹویٹ کیا
Semi-serious proposal if you're having Amazon-style problems with Coding Agents.
Aidan Cunniffe@aidandcunniffe
English
The spec is what you built and why.
yenkel@yenkel
I mean, I've rarely seen such a detailed PRD that mixed product requirements with technical specification, was kept up to date over time, etc. you still have some spec, or you can iterate on the feature with the agent directly and the spec lives in prompt history and you can use @usegitai to keep around as future context but you get the gist about the high level, BDUF PRD being dead
English
Git AI now lets you use past prompts as context — across agents. Whenever you're building on top of AI-code the original prompts help inform what the agent writes next.
Claude knows and adheres to the requirements you gave Cursor. Codex knows about an architecture decision you made in OpenCode. All your agents remember your intent and why they wrote code the way they did.
Get more of your team on Git AI and all your team's agents get smarter.
English