开发者工具1 month ago
Home — AI Code Documentation Generator | DocFlow
在GitHub pull requests上自动生成代码文档。
Aldasams · HN
Show HN: DocFlow – AI documentation updates for GitHub pull requests
完整作品展
技术栈
21 projects
在GitHub pull requests上自动生成代码文档。
Aldasams · HN
Show HN: DocFlow – AI documentation updates for GitHub pull requests
Voidocs 为初创团队创建专业文档，无需代码配置。
@hannah24_app · X
AI驱动的工程团队，规划、构建、测试和发布代码，具有人类监督。
@edgex11lz · X
FizzBee 是 AI 需求工程师，为编程 agent 生成经过验证的规格说明。
jayaprabhakar · HN
I've been building an open source formal methods system (fizzbee.io) for the past few years. Today I'm launching a new app built on the same technology. It performs requirements engineering using formal verification to uncover gaps and produce precise instructions for your coding agents to follow. When given a prompt, it - asks high signal follow-up questions - converts to formal spec and identifies complex requirements gaps - generates validation scenario At the end, it produces a specification document that can be shared with coding agents. In my trials on various projects, it produces working code in fewer iterations. Please give it a try and share your feedback. https://fizzbee.ai/ You can also look at a sample project. https://fizzbee.ai/projects/94bf2869-97a1-445c-8f5d-4445848b...
用 AI 为 Unity、Godot 和 Unreal 生成生产就绪代码和游戏设计文档。
@TopvonA · X
支持15+编程语言、云工作区和编程面试工具的免费在线IDE。
aashhuttossh · HN
Codeground – run and share code in the browser
上传代码让 VibeGuard AI 自动检测安全风险。
@POONAMSING9999 · X
Forget this fight. The problem in AI is vibe coding security risk so i made vibe Guard ai that analysis user code and found out security risks. For the sake of humanity, to solve a painful problem I made this It had free version try now
VibeGuard AI — 分析代码安全漏洞，检查代码是否安全。
@POONAMSING9999 · X
Technology is getting better everyday so the vibe coding but still people loosing money.🚀 Around 62% of vibecode is unsecure. I made VibeGuard that analysis code and check whether it is safe,ready to go,every error and what it can cause, many more...
为Claude Code和Codex设计的开源遥控器，支持iOS、Android和网页。
@Ex3NDR · X
Few days ago Happy had a birthday. Tried to refresh one of the most neglected part of it: our Happy Website: also i built a new harness called “rig”. i started to use at work recently instead of codex/claude code and i liked how it does work. i want to share this with everyone. it is a codex and cause code reimplemented using Pi, but keeping native prompts and expanded a little for uniformity (like added workflows to codex yay!). when something new released that is worthy of porting - i ask Sol to mim for prompts or read sources directly and i can have a feature within an hour. why this is needed? i was constantly blocked by the needing of integrating a lot of models together, which each has their own harness or many doesn’t have any, but i didn’t want to go too far from native and don’t like the idea of extensions - i want experience to be the same everywhere. i think configuration > extensions. more soon