开发者工具5 days ago
Odd Eye — Understand your code before asking AI to fix it
在请AI修改代码前,先理解代码流程和应用连接。
@minmuner_devlog · X
Thanks for the feedback; I’m open to anything.
完整作品展
技术栈
60 projects
在请AI修改代码前,先理解代码流程和应用连接。
@minmuner_devlog · X
Thanks for the feedback; I’m open to anything.
AI agents 构建您的 API 集成，当其发生故障时自动修复。
@getselfheal · X
SelfHeal - integrations that fix themselves. Vendor changes their API at 2am? The agent rewrites the connector, tests it, redeploys. You sleep. Demo (it breaks + heals on camera):
VibeDoctor 扫描 AI 编码应用的安全、性能和代码质量问题。
@Vibedoctor_io · X
Connect VibeDoctor MCP to Cursor, Copilot, Claude Code or Windsurf. Your agent gets a security gate built in. #ClaudeCode #AppSecurity #DevTools
检查你的 AI 应用的安全性、隐私和治理准备情况。
u/Budget_Lawfulness_33 · Reddit
I made a tool that bridges the gap between vibe coding and actually knowing what you shipped A lot of people are shipping things they don’t fully understand anymore. With the new flagship models such Claude/Codex and people spending hundreds on AI subscriptions to build faster, apps are being shipped quicker than ever. But when you’re constantly throwing prompts at AI, adding features, and moving fast, it’s easy to lose track of what actually made it into your codebase. So I built: https
扫描AI账单找出浪费支出，用防篡改证据证明节省成本。
@askrashidkhan · X
为开发者设计的笔记应用，支持代码块、看板管理和GitHub导入。
@SinghApurv1711 · X
Hey! Check it out here:
审查生产环境中的 agent traces，识别并修复反复出现的失败问题
@guru3s · X
IMF team for when your AI agent ( Ethan Hunt ) is about to fail v0 at
重试失败的 Stripe 收费，通过自动化催收流程恢复订阅。
@Holdfast_app · X
将CVE漏洞数据转换为机器可读风险信号，供AI代理和自动化系统使用。
robert_marshall5 · Product Hunt
attestd CVE and supply chain risk signals for autonomous AI agents.
免费网站分析器和SEO审计工具——在60秒内扫描任何网站的性能、SEO、安全、无障碍和UI/UX问题。修复影响您排名的问题。
@WebScore_now · X
在浏览器中编写和运行代码，具有 AI 代码生成和自动修复功能。
@anish2good · X
捕获UI元素及其代码上下文，与AI代理分享以调试视觉缺陷。
Loerei · HN
I found that describing where a broken UI is and taking screenshots for AI agents really sucks. I’m too lazy to explain an indescribable visual bug or capture a millisecond-long flash. I also don’t want to remember which file defines an element, whether it's right in the .tsx or a problem with the Parent Styles in .css. And even if you can point out the exact file, your agent still has to dig through thousands of lines of code to know what on earth you're yapping about. In a 7700-file monorepo like Cal.com, simply giving the right file in the prompt for your agent saves about 68.9% of execution time and 94.2% of the tokens your agent needs to digest. HoverSource gives all the needed information and further pushes it to -88.5% time and -94.5% tokens, basically skipping the entire digging session and jumping straight to reasoning and executing. The save is linear to how big your codebase is. I want to save tokens, but don’t want to spend my time and energy digging manually, and a junio