kageiit

6 ms·

1.
by kageiit 3mo ago
gitar.ai is flat with no limits
2.
Make your codebase agent ready(gitar.ai)
1 points by kageiit 7mo ago|1 comments
3.
by kageiit 7mo ago
Agent-ready and human-friendly are the same thing. With agents writing most code, its a good time to invest in making codebases agent-ready.
4.
We switched to a 5x cheaper LLM. Our costs went up(gitar.ai)
1 points by kageiit 7mo ago|1 comments
5.
by kageiit 7mo ago
Gitar runs multiple specialized AI agents on every code change. They review code, fix CI failures, execute custom repository rules as workflows, and respond to developer feedback in-thread. That's easily 50-100 LLM calls per PR, and co
6.
by kageiit 8mo ago
Fixed link https://gitar.ai/blog/we-sent-our-code-review-ai-to-moltbook
7.
by kageiit 8mo ago
This was an interesting experiment for us. Lot of cool learnings regardless of the hype
8.
We sent our Code Review AI to Moltbook(gitar.ai)
2 points by kageiit 8mo ago|2 comments
9.
by kageiit 8mo ago
We built our own harness from the ground up to account for this Secrets come from aws secret manager and never injected into env directly. Each part of the agentic workflow only gets the secrets it needs injected. Agent can see env var name
10.
AI Code Review Without the Comment Spam(gitar.ai)
5 points by kageiit 8mo ago|1 comments
11.
by kageiit 2y ago
Feature flags are great for safely releasing features fast. As you add more of them though, they add tech debt and make the code harder to reason about. Developers are rarely motivated to clean them up after rollout.
12.
by kageiit 3y ago
I was leading such a team at previous employer focused on building integrating various tools to turn this tool soup into something palatable. The main challenge is the increasing complexity of software and processes that necessitate such to
13.
by kageiit 3y ago
I feel this advice has some merit when dealing with oss projects, systems/backend or small teams. It tends to break apart when working with large teams or when working on mobile apps where one can't just rollback a change easily a
14.
by kageiit 3y ago
I feel like the number of reviewers should be predicated more on how well the reviewers understand the relevant part of the code review. Most code review tooling is too coarse in the sense that it expects a small number of reviewers to know
15.
by kageiit 3y ago
For many use cases, cold-blooded software is not viable. We need better tools to automate and remove the tedium involved in upgrading dependencies or modernizing codebases to protect against ever evolving threats and adapt to changes in the
16.
by kageiit 3y ago
Huge fan of the Arc browser. The UX is really smooth and intuitive. It also declutters UI and provides some nice hints. I usually go to the url box to copy the url. one day, it suggested me to use a keyboard shortcut instead based on how of
17.
by kageiit 3y ago
Have you considered using something like a treesitter grammar? It could solve the editor specific uses cases like highlighting and even linting as it creates asts that are more amenable for a language server implementation
18.
by kageiit 3y ago
I feel if the product is valuable enough and solves a real pain point, even if the backing company dies, an alternative will take its place. I have also seen models where the source is made available just before that happens. For eg: https
19.
by kageiit 3y ago
I setup codeql locally to do some simple taint analysis recently. I found the tooling very powerful but quite complex to use. Updating the codeql database after making code changes was quite slow as well which made it harder to do increment
20.
by kageiit 9y ago
Hey everyone! I'm Gautam and I tech-lead this project. Happy to answer any questions/give insights on how we approached this