Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Announcing the latest release from Qodo: Modern engineering runs across hundreds of repos, dozens of teams, and AI that writes code faster than anyone can review it. Today, Qodo releases features built for these teams. - Cross Repo Review: Qodo now maps dependencies across your repos and catches breaking...

QodoAI's profile picture

Qodo

19,706 subscribers

633,155 görüntüleme • 3 ay önce •via X (Twitter)

Bilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

11 Yorum

Qodo profil fotoğrafı
Qodo3 ay önce

Read the full break down in a blog post here:

Nikki Siapno profil fotoğrafı
Nikki Siapno3 ay önce

Cross-repo reviews makes a lot of sense. Great release!

Tech with Mak profil fotoğrafı
Tech with Mak3 ay önce

Congratulations to the team on shipping these fantastic features, really impressive work!

Raul Junco profil fotoğrafı
Raul Junco3 ay önce

This is how we get real engineering Context.

Petar Ivanov profil fotoğrafı
Petar Ivanov3 ay önce

Yesss, this new feature by Qodo is a banger!

Shrey shah profil fotoğrafı
Shrey shah3 ay önce

Amazing work team!!

Sofia 🌷 💙 ❤️ profil fotoğrafı
Sofia 🌷 💙 ❤️3 ay önce

Facts!

Shamim Hossain profil fotoğrafı
Shamim Hossain3 ay önce

That’s great

Lily Anderson profil fotoğrafı
Lily Anderson2 ay önce

Looks like a powerful update for engineering teams. Cross-repo reviews and dependency awareness can make AI-assisted code reviews much more reliable at scale. 🚀

Victoria Blake profil fotoğrafı
Victoria Blake3 ay önce

Impressive update from the Qodo team. We'd love to collaborate and help showcase these AI-powered engineering innovations to a broader developer and tech audience. Let's connect. 🚀🤝

安叫兽|Bird🕊️ 🔶 BNB profil fotoğrafı
安叫兽|Bird🕊️ 🔶 BNB3 ay önce

跨库依赖这块真是大团队的痛点了

Benzer Videolar

AI can write more code than any team can review by hand, and a pull request can look fine while hiding a security issue or missing a requirement. In our new short course, AI Code Review, built in collaboration with Qodo and taught by Nnenna, you'll learn the practices that make AI code review effective: review before you open a pull request, give the reviewer full context about your codebase, and triage findings by risk. Then you'll build your own review agent, from a context engine that finds the right code to a team of specialized reviewers. Enroll for free:
1:39

AI can write more code than any team can review by hand, and a pull request can look fine while hiding a security issue or missing a requirement. In our new short course, AI Code Review, built in collaboration with Qodo and taught by Nnenna, you'll learn the practices that make AI code review effective: review before you open a pull request, give the reviewer full context about your codebase, and triage findings by risk. Then you'll build your own review agent, from a context engine that finds the right code to a team of specialized reviewers. Enroll for free:

DeepLearning.AI

56,896 görüntüleme • 2 ay önce

2025 is the year of the CLI, not 𝘥𝘦𝘴𝘱𝘪𝘵𝘦 its simplicity but 𝘣𝘦𝘤𝘢𝘶𝘴𝘦 of it. I’m thrilled to share today’s announcement. It’s a milestone for Qodo’s mission, and for every team that wants to put AI to work across the SDLC. Let’s dive in! 𝐌𝐞𝐞𝐭 𝐐𝐨𝐝𝐨 𝐆𝐞𝐧 𝐂𝐋𝐈 Built for creating, running, and managing AI agents that automate critical development tasks across the SDLC, from analyzing CI tests and logs to triaging production errors and more. 𝐊𝐞𝐲 𝐟𝐞𝐚𝐭𝐮𝐫𝐞𝐬 ✅ Runs everywhere ✅ Designed for task execution, not just Q&A ✅ Trigger from CI, hooks, or cloud functions—you choose ✅ Works with all major models ✅ Fully customizable agents with their own tools, credentials, and goals And yes, it plays nicely with our other Qodo agents too (e.g., Qodo Merge, the AI code-review tool). This isn’t just about writing code—it’s about catching bugs earlier, automating deeper, and shipping higher-quality software. 𝐓𝐫𝐲 𝐢𝐭 𝐭𝐨𝐝𝐚𝐲 𝐢𝐧 𝐬𝐞𝐜𝐨𝐧𝐝𝐬 Make sure you have npm installed, then run: npm install -g @qodo/gen Oh, one more thing- 𝐄𝐱𝐩𝐥𝐨𝐫𝐞 𝐨𝐮𝐫 𝐥𝐢𝐛𝐫𝐚𝐫𝐲 𝐨𝐟 𝐬𝐩𝐞𝐜𝐢𝐚𝐥𝐢𝐳𝐞𝐝 𝐐𝐨𝐝𝐨 𝐀𝐠𝐞𝐧𝐭𝐬, and contribute your own so others can benefit!
3:13

2025 is the year of the CLI, not 𝘥𝘦𝘴𝘱𝘪𝘵𝘦 its simplicity but 𝘣𝘦𝘤𝘢𝘶𝘴𝘦 of it. I’m thrilled to share today’s announcement. It’s a milestone for Qodo’s mission, and for every team that wants to put AI to work across the SDLC. Let’s dive in! 𝐌𝐞𝐞𝐭 𝐐𝐨𝐝𝐨 𝐆𝐞𝐧 𝐂𝐋𝐈 Built for creating, running, and managing AI agents that automate critical development tasks across the SDLC, from analyzing CI tests and logs to triaging production errors and more. 𝐊𝐞𝐲 𝐟𝐞𝐚𝐭𝐮𝐫𝐞𝐬 ✅ Runs everywhere ✅ Designed for task execution, not just Q&A ✅ Trigger from CI, hooks, or cloud functions—you choose ✅ Works with all major models ✅ Fully customizable agents with their own tools, credentials, and goals And yes, it plays nicely with our other Qodo agents too (e.g., Qodo Merge, the AI code-review tool). This isn’t just about writing code—it’s about catching bugs earlier, automating deeper, and shipping higher-quality software. 𝐓𝐫𝐲 𝐢𝐭 𝐭𝐨𝐝𝐚𝐲 𝐢𝐧 𝐬𝐞𝐜𝐨𝐧𝐝𝐬 Make sure you have npm installed, then run: npm install -g @qodo/gen Oh, one more thing- 𝐄𝐱𝐩𝐥𝐨𝐫𝐞 𝐨𝐮𝐫 𝐥𝐢𝐛𝐫𝐚𝐫𝐲 𝐨𝐟 𝐬𝐩𝐞𝐜𝐢𝐚𝐥𝐢𝐳𝐞𝐝 𝐐𝐨𝐝𝐨 𝐀𝐠𝐞𝐧𝐭𝐬, and contribute your own so others can benefit!

Itamar Friedman

11,811 görüntüleme • 1 yıl önce

garry tan just open-sourced a 128k-star repo that basically turns claude code into your entire engineering org it’s called gstack: 23 tools that break a single claude workflow into product, engineering, qa, review, and release lanes > /office-hours turns a rough idea into a real product spec > /plan-ceo-review + /plan-eng-review try to tear the plan apart before any code ships > /review hunts for bugs and patches them > /qa spins up an actual browser and tests the app end to end > /ship runs the final checks and pushes the pr think → plan → build → review → test → ship → reflect garry says this setup let him ship 3 production services and 40+ features in 60 days while still running yc full-time one developer sets the compass. the repo runs the loop.
0:36

garry tan just open-sourced a 128k-star repo that basically turns claude code into your entire engineering org it’s called gstack: 23 tools that break a single claude workflow into product, engineering, qa, review, and release lanes > /office-hours turns a rough idea into a real product spec > /plan-ceo-review + /plan-eng-review try to tear the plan apart before any code ships > /review hunts for bugs and patches them > /qa spins up an actual browser and tests the app end to end > /ship runs the final checks and pushes the pr think → plan → build → review → test → ship → reflect garry says this setup let him ship 3 production services and 40+ features in 60 days while still running yc full-time one developer sets the compass. the repo runs the loop.

CyrilXBT

20,997 görüntüleme • 1 ay önce

Today I am excited to announce Greptile’s BIGGEST update ever 💥 Greptile is the AI code review bot loved by over 3,000 software teams across the world. We’re launching four things today: 🧠 Long-term memory for the code review agent so it can intelligently learn your company's idiosyncrasies and best practices 🤝 Ability to connect your Jira, Google Docs, and Notion via MCP so Greptile can have more context 🎯 Ability to create highly scoped rules that only apply to certain repos and file patterns 💰 A simpler, more predictable pricing model of flat $30/month/developer. Let’s dive in 🧵
0:59

Today I am excited to announce Greptile’s BIGGEST update ever 💥 Greptile is the AI code review bot loved by over 3,000 software teams across the world. We’re launching four things today: 🧠 Long-term memory for the code review agent so it can intelligently learn your company's idiosyncrasies and best practices 🤝 Ability to connect your Jira, Google Docs, and Notion via MCP so Greptile can have more context 🎯 Ability to create highly scoped rules that only apply to certain repos and file patterns 💰 A simpler, more predictable pricing model of flat $30/month/developer. Let’s dive in 🧵

Daksh Gupta

246,046 görüntüleme • 1 yıl önce

Every company needs killer Skills library. Not a folder in GitHub that 10% of the company knows how to use. A living library the whole company benefits from. The best deal review skill gets better every time a sales rep uses it. A great research skill gets discovered instead of rebuilt 50 times. Creating a skill should be as easy as asking to create something useful from based on the context of your work. And the top skills (and skill creators) should rise to the top. Create, share, collaborate on, discover and understand usage of skills, organize them into databases by team or use case, then use them across any of your agents. Still early, but the idea is to make Notion the best home for your company’s collective AI skills. Made a quick demo (all available now)!
1:59

Every company needs killer Skills library. Not a folder in GitHub that 10% of the company knows how to use. A living library the whole company benefits from. The best deal review skill gets better every time a sales rep uses it. A great research skill gets discovered instead of rebuilt 50 times. Creating a skill should be as easy as asking to create something useful from based on the context of your work. And the top skills (and skill creators) should rise to the top. Create, share, collaborate on, discover and understand usage of skills, organize them into databases by team or use case, then use them across any of your agents. Still early, but the idea is to make Notion the best home for your company’s collective AI skills. Made a quick demo (all available now)!

Hurley

699,569 görüntüleme • 1 ay önce

📱 AI Assistant, now on all your devices AI Assistant is now available on phones and tablets for all Evernote users. Wherever you are, you can organize notes, research ideas, create content, and interact with everything in your Evernote account through a simple chat. These two new features are also available on mobile with the AI Assistant: ⚡ AI Prompts let you save repeatable instructions to automate workflows, generate reports, review your work, and much more, using the content and context in your Evernote. 🧠 AI Memory lets AI Assistant remember your preferences across conversations. Just say “Remember to…” or “Store this in your memory for future conversations.” Update your Evernote app or download it now to get started! Available from version version 11.23.2.
0:50

📱 AI Assistant, now on all your devices AI Assistant is now available on phones and tablets for all Evernote users. Wherever you are, you can organize notes, research ideas, create content, and interact with everything in your Evernote account through a simple chat. These two new features are also available on mobile with the AI Assistant: ⚡ AI Prompts let you save repeatable instructions to automate workflows, generate reports, review your work, and much more, using the content and context in your Evernote. 🧠 AI Memory lets AI Assistant remember your preferences across conversations. Just say “Remember to…” or “Store this in your memory for future conversations.” Update your Evernote app or download it now to get started! Available from version version 11.23.2.

Evernote

11,315 görüntüleme • 2 ay önce

.Postman is now natively available in your favorite coding agent! The new Postman CLI is designed to bring API engineering for agents: 1️⃣ Works in Git and your code repo - Just drop Postman where your agent lives and works. 2️⃣ No GUI - Work in your coding agent. Bring up the Postman UI for review and approval. 3️⃣ No sign-up - Get started right away. Sign-up when you have to save your work and want more. Install once, work in your agent. Run npm install -g postman-cli, then postman init. This loads Postman's skills into your coding agent so it can create collections, write tests, and much more. Available as a plugin for all coding agents! The skills cover the API lifecycle: find APIs your org already has, generate tests that catch regressions, mock an API before it exists, watch live endpoints for downtime and drift, run checks in CI on every commit, and run performance tests. You can also extend the abilities of your agent with the Context Graph. An agent often sees only the code that is accessible to them. The Context Graph API gives it a map of your team's infrastructure, APIs, and services, and how they depend on each other. As your agent works, you stay the reviewer. Your agent does the work from the command line. Open Postman when you want to review or approve it. Check out more at
0:37

.Postman is now natively available in your favorite coding agent! The new Postman CLI is designed to bring API engineering for agents: 1️⃣ Works in Git and your code repo - Just drop Postman where your agent lives and works. 2️⃣ No GUI - Work in your coding agent. Bring up the Postman UI for review and approval. 3️⃣ No sign-up - Get started right away. Sign-up when you have to save your work and want more. Install once, work in your agent. Run npm install -g postman-cli, then postman init. This loads Postman's skills into your coding agent so it can create collections, write tests, and much more. Available as a plugin for all coding agents! The skills cover the API lifecycle: find APIs your org already has, generate tests that catch regressions, mock an API before it exists, watch live endpoints for downtime and drift, run checks in CI on every commit, and run performance tests. You can also extend the abilities of your agent with the Context Graph. An agent often sees only the code that is accessible to them. The Context Graph API gives it a map of your team's infrastructure, APIs, and services, and how they depend on each other. As your agent works, you stay the reviewer. Your agent does the work from the command line. Open Postman when you want to review or approve it. Check out more at

Abhinav Asthana

493,187 görüntüleme • 10 gün önce

My whole company runs on skills I bundled into a GitHub repo. Here's how to build the same thing for your team: - Put your skills in a GitHub repo - Get Claude to write the couple of JSON files that make it readable as a plugin - In Claude Code, type /plugin, go to marketplaces, add marketplace, paste your repo URL - Split the plugins by department, so your copywriter isn't installing the finance skills It works in Codex too. I've got the same team skills installed there and I use them the same way. Now when I build something like my Notion formatting skill, I add it to the repo and it lands on everyone's Claude and Codex. If someone wrecks a skill, we roll it back to an older version. The key is enabling auto-update, so when someone improves a skill everyone benefits. I don't have a clue how the JSON works. I got Claude to set the whole thing up for me. Start with one skill and before you know it your whole team will be AI pilled.
5:18

My whole company runs on skills I bundled into a GitHub repo. Here's how to build the same thing for your team: - Put your skills in a GitHub repo - Get Claude to write the couple of JSON files that make it readable as a plugin - In Claude Code, type /plugin, go to marketplaces, add marketplace, paste your repo URL - Split the plugins by department, so your copywriter isn't installing the finance skills It works in Codex too. I've got the same team skills installed there and I use them the same way. Now when I build something like my Notion formatting skill, I add it to the repo and it lands on everyone's Claude and Codex. If someone wrecks a skill, we roll it back to an older version. The key is enabling auto-update, so when someone improves a skill everyone benefits. I don't have a clue how the JSON works. I got Claude to set the whole thing up for me. Start with one skill and before you know it your whole team will be AI pilled.

The Startup Ideas Podcast (SIP) 🧃

19,532 görüntüleme • 1 ay önce

Explaining a product change often takes longer than making it. This AI can now build the change for your engineers to review. Small product fixes often have to wait because only engineers can make changes to the code: → A typo in the copy → An empty screen with no helpful message → A missing form field → A bug someone found but can't fix Base Code by Base44 lets anyone build these fixes on your existing code, right from your browser. Here's how it works: • Connect the GitHub repository your engineers already use • Describe the change in plain language • Base Code builds the change for you • Preview your real product running with the change • The change comes back to your engineers as a normal pull request Your engineers stay in control the whole time: ✅ Base Code never pushes to your default branch ✅ Your existing checks and protections still apply ✅ Engineers decide what gets merged No local setup is needed. For now, Base Code works with GitHub only. You can try it for free for 30 days: ↳ One invite covers your whole team ↳ Credits are included, so you can test it properly 📌 Try it here: 🎁 Use this coupon code: IC-79AD21-74794F-3CEF13-C80813 (valid for first 50 users) 🔄 Repost to help others turn product requests into real changes
0:27

Explaining a product change often takes longer than making it. This AI can now build the change for your engineers to review. Small product fixes often have to wait because only engineers can make changes to the code: → A typo in the copy → An empty screen with no helpful message → A missing form field → A bug someone found but can't fix Base Code by Base44 lets anyone build these fixes on your existing code, right from your browser. Here's how it works: • Connect the GitHub repository your engineers already use • Describe the change in plain language • Base Code builds the change for you • Preview your real product running with the change • The change comes back to your engineers as a normal pull request Your engineers stay in control the whole time: ✅ Base Code never pushes to your default branch ✅ Your existing checks and protections still apply ✅ Engineers decide what gets merged No local setup is needed. For now, Base Code works with GitHub only. You can try it for free for 30 days: ↳ One invite covers your whole team ↳ Credits are included, so you can test it properly 📌 Try it here: 🎁 Use this coupon code: IC-79AD21-74794F-3CEF13-C80813 (valid for first 50 users) 🔄 Repost to help others turn product requests into real changes

Andrew Bolis

40,165 görüntüleme • 11 gün önce

A DEVELOPER FOUND SEVEN WAYS TO TAKE DOWN A PRODUCTION DATABASE THAT ALL LOOK EXACTLY LIKE NORMAL, INNOCENT CODE AND ALMOST EVERY TEAM IS SHIPPING AT LEAST ONE OF THEM RIGHT NOW 17 minutes from Josh Berkus, one of the people who actually maintains PostgreSQL, walking through the quiet mistakes that turn a healthy database into a 3am outage. -> The moment it lands, you realize none of these are exotic attacks. They're ordinary-looking decisions -- a query that locks a table, a connection that never closes, a setting no one ever questioned -- that work perfectly until the day they don't, and then they take everything down with them. The scary part isn't that the database breaks. It's how normal the code looks right up until it does. A query that runs in 5ms on your laptop and 5 minutes on prod. A migration that silently locks the whole table. A connection pool that runs dry the moment real traffic shows up. Every one of them passed review. Writing SQL that runs was never the hard part -> writing SQL that survives production is. And now that an AI agent is generating and firing queries at your real database faster than anyone can read them, every one of those seven landmines is one autocomplete away -- and the only person who can stop it is the one who already knows where they're buried. Your database doesn't go down because someone attacked it. It goes down because something that looked completely normal finally caught up with it. Save and Watch it today. You'll see the next outage coming before it lands ↓
16:51

A DEVELOPER FOUND SEVEN WAYS TO TAKE DOWN A PRODUCTION DATABASE THAT ALL LOOK EXACTLY LIKE NORMAL, INNOCENT CODE AND ALMOST EVERY TEAM IS SHIPPING AT LEAST ONE OF THEM RIGHT NOW 17 minutes from Josh Berkus, one of the people who actually maintains PostgreSQL, walking through the quiet mistakes that turn a healthy database into a 3am outage. -> The moment it lands, you realize none of these are exotic attacks. They're ordinary-looking decisions -- a query that locks a table, a connection that never closes, a setting no one ever questioned -- that work perfectly until the day they don't, and then they take everything down with them. The scary part isn't that the database breaks. It's how normal the code looks right up until it does. A query that runs in 5ms on your laptop and 5 minutes on prod. A migration that silently locks the whole table. A connection pool that runs dry the moment real traffic shows up. Every one of them passed review. Writing SQL that runs was never the hard part -> writing SQL that survives production is. And now that an AI agent is generating and firing queries at your real database faster than anyone can read them, every one of those seven landmines is one autocomplete away -- and the only person who can stop it is the one who already knows where they're buried. Your database doesn't go down because someone attacked it. It goes down because something that looked completely normal finally caught up with it. Save and Watch it today. You'll see the next outage coming before it lands ↓

slash1s

22,268 görüntüleme • 4 ay önce

The Clark County Election Department is introducing a new step in the in-person voting process in 2026. The check-in process and voting machines (now called ballot marking devices) will remain the same as in recent elections. But now, once a voter makes their selections, they get a printout of their ballot to review before submitting it through the new tabulators. This change aligns with statewide security standards and national best practices. By producing a paper ballot, every voter can easily review their selections before casting their vote. Paper records are then safely stored for audits and recounts if needed.
0:52

The Clark County Election Department is introducing a new step in the in-person voting process in 2026. The check-in process and voting machines (now called ballot marking devices) will remain the same as in recent elections. But now, once a voter makes their selections, they get a printout of their ballot to review before submitting it through the new tabulators. This change aligns with statewide security standards and national best practices. By producing a paper ballot, every voter can easily review their selections before casting their vote. Paper records are then safely stored for audits and recounts if needed.

Clark County Nevada

18,982 görüntüleme • 9 ay önce

Obsidian Bases are better than Notion databases. Most people never use them because they're too technical. This Claude skill changes this: Bases automatically aggregate notes from your vault into a structured table. I have dozens of bases; the one in the video replaces the reference manager, for instance. Problem: Most struggle with setting them up. There's now a skill built by one of the Obsidian developers that runs inside Claude. The skill scans your vault and automatically generates the base. The hardest Obsidian feature to learn. Solved with one sentence.
1:53

Obsidian Bases are better than Notion databases. Most people never use them because they're too technical. This Claude skill changes this: Bases automatically aggregate notes from your vault into a structured table. I have dozens of bases; the one in the video replaces the reference manager, for instance. Problem: Most struggle with setting them up. There's now a skill built by one of the Obsidian developers that runs inside Claude. The skill scans your vault and automatically generates the base. The hardest Obsidian feature to learn. Solved with one sentence.

Ilya Shabanov

34,406 görüntüleme • 5 ay önce

A DEVELOPER WHO HELPS MAINTAIN GIT ITSELF PROVED THAT USING GIT AND CONTRIBUTING WITH GIT ARE TWO DIFFERENT SKILLS AND ALMOST NO ONE LEARNS THE SECOND 55 minutes from Johannes Schindelin, one of git's most prolific contributors, on the workflow that gets your code accepted into a project you don't own. -> The moment it lands, committing to your own repo turns out to be the easy 10%. Landing a change in someone else's codebase is the part nobody taught you. Most people can save their own work. Far fewer can revise a patch five times, keep the history clean, and merge it into a project moving under them. Saving your code was never the skill -> getting it merged into someone else's is. And when an AI agent fires off a pull request nobody asked for, the person who knows how to really contribute is the one who gets it accepted instead of closed. Anyone can commit to their own repo. The person who can land a change in a project they don't own is the one who actually ships. Bookmark & Watch it today ↓
55:43

A DEVELOPER WHO HELPS MAINTAIN GIT ITSELF PROVED THAT USING GIT AND CONTRIBUTING WITH GIT ARE TWO DIFFERENT SKILLS AND ALMOST NO ONE LEARNS THE SECOND 55 minutes from Johannes Schindelin, one of git's most prolific contributors, on the workflow that gets your code accepted into a project you don't own. -> The moment it lands, committing to your own repo turns out to be the easy 10%. Landing a change in someone else's codebase is the part nobody taught you. Most people can save their own work. Far fewer can revise a patch five times, keep the history clean, and merge it into a project moving under them. Saving your code was never the skill -> getting it merged into someone else's is. And when an AI agent fires off a pull request nobody asked for, the person who knows how to really contribute is the one who gets it accepted instead of closed. Anyone can commit to their own repo. The person who can land a change in a project they don't own is the one who actually ships. Bookmark & Watch it today ↓

slash1s

12,797 görüntüleme • 4 ay önce

Introducing Video Skills. AI video tools have come a long way in the past year. But our customers—large companies with extremely specific brand standards—keep telling us the same thing: these tools still don’t cut it. Video Skills changes that. Creative and brand teams can now build and deploy Video Skills across the company, giving marketing, sales and education teams a guided way to create fully brand-approved videos in Claude or ChatGPT. — Your creative briefs and workflows — Your assets and motion systems — Fully editable output — Collaborative editing — No slop Built for enterprises ready to scale video for real.
1:27

Introducing Video Skills. AI video tools have come a long way in the past year. But our customers—large companies with extremely specific brand standards—keep telling us the same thing: these tools still don’t cut it. Video Skills changes that. Creative and brand teams can now build and deploy Video Skills across the company, giving marketing, sales and education teams a guided way to create fully brand-approved videos in Claude or ChatGPT. — Your creative briefs and workflows — Your assets and motion systems — Fully editable output — Collaborative editing — No slop Built for enterprises ready to scale video for real.

Champ 🤟🏻

613,697 görüntüleme • 2 ay önce

For those of you tired of yet another AI-based IDE: Check out Traycer. It's a Visual Studio Code extension (free forever for anyone working on open-source repositories), and it does something different from everyone else. You write a high-level prompt outlining the changes you want to make to your codebase, and the extension generates a plan for you before you touch the code. (It reminds me of GitHub Copilot Workspaces.) You can review the plan, understand exactly the changes the extension will make to your code, and make any modifications. When you are ready, you execute the plan, and Traycer stages all of the changes so you have a new opportunity to review everything. Only then does Traycer apply the changes. This is ideal for large codebases where you'd rather study the changes the AI plans to make before they make it into your code. Look at the video I recorded to see how it works. Thanks to the Traycer team for collaborating with me on this post!
7:27

For those of you tired of yet another AI-based IDE: Check out Traycer. It's a Visual Studio Code extension (free forever for anyone working on open-source repositories), and it does something different from everyone else. You write a high-level prompt outlining the changes you want to make to your codebase, and the extension generates a plan for you before you touch the code. (It reminds me of GitHub Copilot Workspaces.) You can review the plan, understand exactly the changes the extension will make to your code, and make any modifications. When you are ready, you execute the plan, and Traycer stages all of the changes so you have a new opportunity to review everything. Only then does Traycer apply the changes. This is ideal for large codebases where you'd rather study the changes the AI plans to make before they make it into your code. Look at the video I recorded to see how it works. Thanks to the Traycer team for collaborating with me on this post!

Santiago

84,497 görüntüleme • 1 yıl önce

Your Plan SUCKS! 👀 Inspired by the legend Andrej Karpathy himself, I created a new skill: LLM Council. Create better plans, by committee. Supports: > Codex CLI > Gemini CLI > Claude Code > OpenCode Call the skill with your feature that you'd like to build. It will ask you some clarifying question, and then launch up to four parallel planning agents to create a detailed plan. Once the plans are in, all plans are anonymized and the "The Judge" will critique and choose the best plan *OR* the best parts from all of them. Finally, it will output a final-plan, which you can review and refine. I even created a nice UI for you to review and refine your plans. This Skill has been tested on Linux only, but should work on other platforms. Please report any bugs! Links in the comments.
0:28

Your Plan SUCKS! 👀 Inspired by the legend Andrej Karpathy himself, I created a new skill: LLM Council. Create better plans, by committee. Supports: > Codex CLI > Gemini CLI > Claude Code > OpenCode Call the skill with your feature that you'd like to build. It will ask you some clarifying question, and then launch up to four parallel planning agents to create a detailed plan. Once the plans are in, all plans are anonymized and the "The Judge" will critique and choose the best plan *OR* the best parts from all of them. Finally, it will output a final-plan, which you can review and refine. I even created a nice UI for you to review and refine your plans. This Skill has been tested on Linux only, but should work on other platforms. Please report any bugs! Links in the comments.

am.will

69,134 görüntüleme • 8 ay önce

#1 skill for developers in 2026: Automate everything you can using AI. I bet my lunch your team is dealing with all of these: • Stale documentation • Outdated dependencies • Poor test coverage • Deprecated APIs Every company I work with has these same problems. You can solve all of these right now. Automatically. Using AI. Here are 3 examples. Watch the attached video: I'm using Ona Automations to tackle this. These are background agents that run in the cloud, in a fully configured dev environment with your toolchain, your dependencies, and your services. You can run an unlimited number of these agents in parallel and across all your repositories. Claude Code and Codex only run locally, so they are hard to scale, and you can't run them when your computer is closed. Ona runs in the cloud. Here are the three examples: 1. Test coverage Run a nightly automation to identify any untested code paths, generate candidate tests, verify they pass, and open draft PRs. You wake up every morning to PRs that improve your test coverage. 2. Dependency upgrades Configure a weekly automation that bumps a dependency version, runs your full test suite, and reports any regressions. If everything is clean, it opens a PR. If something breaks, it opens a report so you can decide what to do. 3. Documentation auditing Set up a weekly automation that checks recent commits against your README file and setup guides, identifies broken examples and outdated instructions, and opens a PR with fixes.
5:18

#1 skill for developers in 2026: Automate everything you can using AI. I bet my lunch your team is dealing with all of these: • Stale documentation • Outdated dependencies • Poor test coverage • Deprecated APIs Every company I work with has these same problems. You can solve all of these right now. Automatically. Using AI. Here are 3 examples. Watch the attached video: I'm using Ona Automations to tackle this. These are background agents that run in the cloud, in a fully configured dev environment with your toolchain, your dependencies, and your services. You can run an unlimited number of these agents in parallel and across all your repositories. Claude Code and Codex only run locally, so they are hard to scale, and you can't run them when your computer is closed. Ona runs in the cloud. Here are the three examples: 1. Test coverage Run a nightly automation to identify any untested code paths, generate candidate tests, verify they pass, and open draft PRs. You wake up every morning to PRs that improve your test coverage. 2. Dependency upgrades Configure a weekly automation that bumps a dependency version, runs your full test suite, and reports any regressions. If everything is clean, it opens a PR. If something breaks, it opens a report so you can decide what to do. 3. Documentation auditing Set up a weekly automation that checks recent commits against your README file and setup guides, identifies broken examples and outdated instructions, and opens a PR with fixes.

Santiago

25,804 görüntüleme • 7 ay önce

Today we are introducing 2 key features to JAIGP: AI Review & Open Prompting. AI review is part of 5-step process where papers get feedback from & are evaluated based on their ability to address that feedback. This means they are not stuck in an endless AI review loop. Open prompting is a newer idea. We are making all prompts we used to create JAIGP open, and also, opening up the journal's rules to the community for suggestions. You can suggest the prompt we should run next! So, if you have opinions about AI generated papers, you can share them directly with us at
2:20

Today we are introducing 2 key features to JAIGP: AI Review & Open Prompting. AI review is part of 5-step process where papers get feedback from & are evaluated based on their ability to address that feedback. This means they are not stuck in an endless AI review loop. Open prompting is a newer idea. We are making all prompts we used to create JAIGP open, and also, opening up the journal's rules to the community for suggestions. You can suggest the prompt we should run next! So, if you have opinions about AI generated papers, you can share them directly with us at

César A. Hidalgo

13,453 görüntüleme • 6 ay önce

NVIDIA just released a repo that scans AI agent skills for security risks BEFORE you run them, which matters more than people realize now that everyone's installing random tools, skills, and MCPs from GitHub. I break down that one AND 4 other GitHub repos trending over the last 30 days in this episode of The Startup Ideas Podcast (SIP) 🧃: 1. A skill that kills AI slop finally (better writing) 2. A CRM thats built for AI agents (so you can have agents follow up, reach out etc) 3. An agent that edits your videos for you (so you can focus on creative) 4. An opensource CapCut alternative built for agents (because editing is a headache) All free, all open source. Watch my breakdown of the 5 GitHub repos trending over the last 30 days below The tools people will be talking about in six months are on GitHub today. That's the fun part of digging through GitHub right now.
24:43

NVIDIA just released a repo that scans AI agent skills for security risks BEFORE you run them, which matters more than people realize now that everyone's installing random tools, skills, and MCPs from GitHub. I break down that one AND 4 other GitHub repos trending over the last 30 days in this episode of The Startup Ideas Podcast (SIP) 🧃: 1. A skill that kills AI slop finally (better writing) 2. A CRM thats built for AI agents (so you can have agents follow up, reach out etc) 3. An agent that edits your videos for you (so you can focus on creative) 4. An opensource CapCut alternative built for agents (because editing is a headache) All free, all open source. Watch my breakdown of the 5 GitHub repos trending over the last 30 days below The tools people will be talking about in six months are on GitHub today. That's the fun part of digging through GitHub right now.

GREG ISENBERG

54,582 görüntüleme • 1 ay önce