跳到主内容
@wquguru
精选82VoxAI 产品与模型

Ponytail 5:让 AI Agent 少写代码、提效降本的工具

The new Ponytail 5 is a complete rewrite. Same request, "add a date picker to th…

原文
发到 X
推荐理由

用具体数据对比展示了工具如何改变 AI 的行为模式,结构清晰,对同行有参考价值。

The new Ponytail 5 is a complete rewrite. Same request, "add a date picker to the frontend": without it, the agent wrote 335 lines. With it, 𝗷𝘂𝘀𝘁 𝟭𝟬 𝗹𝗶𝗻𝗲𝘀, using the repo's existing Input component and letting the browser supply the calendar.

新的 Ponytail 5 是一次彻底的重写。同样的需求:“在前端添加日期选择器”:没有它时,智能体写了 335 行代码;有了它后,仅用 10 行代码,利用仓库中现有的 Input 组件,并由浏览器提供日历功能。

In the maker's own benchmark, 39 tasks in Claude Code with Opus 5.5, the agent with Ponytail wrote 53% less code, took 41% less time and cost 26% less. It wrote less, yet 𝟵𝟴% 𝗼𝗳 𝗶𝘁𝘀 𝗿𝗶𝘀𝗸𝘆 𝗹𝗼𝗴𝗶𝗰 𝘀𝗵𝗶𝗽𝗽𝗲𝗱 𝘄𝗶𝘁𝗵 𝗮 𝘁𝗲𝘀𝘁, against 68% without.

在作者自己的基准测试中,使用 Opus 5.5 的 Claude Code 进行了 39 项任务,配备 Ponytail 的智能体少写了 53% 的代码,耗时减少了 41%,成本降低了 26%。虽然代码量更少,但 98% 的风险逻辑都附带了测试,而没有该技能时仅为 68%。

Before writing code, it reads the parts the change touches, then asks these in order and stops at the first one that holds: → Does this have to be written at all? → Is it already in the repo? → Is the standard library enough? → Does the browser or the OS already have it? → Can an installed dependency cover it? → Can it be one line? → If none of that works, write the smallest version that runs, plus one small test if it has logic

在编写代码之前,它会先阅读变更所涉及的代码部分,然后依次询问以下问题,并在找到第一个有答案的问题时停止: → 这是否必须编写? → 仓库中是否已有? → 标准库是否足够? → 浏览器或操作系统是否已具备? → 已安装的依赖是否能覆盖? → 能否只用一行代码实现? → 如果以上都不行,则编写能运行的最小版本,如果涉及逻辑则额外添加一个小测试

Input validation, error handling, security and accessibility never get cut.

输入验证、错误处理、安全性和无障碍性绝不会省略。

Two commands were rebuilt too. /ponytail-review used to look only for code to delete; now it also reads the code your change touches. Rename a field and break a file you never touched, and it catches that. In the maker's tests it found every problem outside the diff, against 78% without the skill. /ponytail-audit runs the same checks across the whole repo and ranks what to fix first.

两个命令也进行了重建。/ponytail-review 过去只查找可删除的代码;现在它还会读取你的变更所涉及的代码。重命名一个字段并破坏了一个你从未触碰的文件,它能捕捉到这一点。在作者的测试中,它能发现 diff 之外的所有问题,而没有该技能时仅为 78%。/ponytail-audit 在整个仓库中运行相同的检查,并对修复优先级进行排序。

5.3 also adds a bar above the Claude Code prompt: what the task cost, its tokens, how long it ran, how much existing code it reused, and whether the tests passed (needs Claude Code 2.1.290 or later).

5.3 版还在 Claude Code 提示符上方增加了一个栏位:显示任务成本、Token 数量、运行时长、复用的现有代码量,以及测试是否通过(需要 Claude Code 2.1.290 或更高版本)。

MIT licensed, 172K stars, 8,000+ more this week. To make your agent look for what already exists before it writes, paste these into Claude Code as two separate prompts: /plugin marketplace add DietrichGebert/ponytail /plugin install ponytail@ponytail

采用 MIT 许可证,拥有 172K 星标,本周新增 8,000+ 个。为了让你的智能体在编写代码前先查找已存在的资源,请将以下内容作为两条单独的提示词粘贴到 Claude Code 中: /plugin marketplace add DietrichGebert/ponytail /plugin install ponytail@ponytail

In Codex, run these two: codex plugin marketplace add DietrichGebert/ponytail codex plugin add ponytail@ponytail Then trust its two hooks in /hooks and start a new thread.

在 Codex 中,运行以下两条命令: codex plugin marketplace add DietrichGebert/ponytail codex plugin add ponytail@ponytail 然后信任 /hooks 中的两个钩子,并开始一个新的线程。

更进一步:量化金融体系

看懂新闻只是起点——沿量化金融路径,把它变成能交付的工程能力

进入量化体系 →

相似阅读

关联信息,但可能不是同一事件