Agent Skills 目录

收到代码评审反馈时、实施建议之前使用，尤其是反馈看起来不清晰或技术上存疑时——需要技术严谨性和验证，而不是表面附和或盲目照做

完成任务、实现重要功能或合并代码前，用于验证工作是否满足需求

在当前会话中执行包含独立任务的实现计划时使用

遇到任何 bug、测试失败或意外行为时，在提出修复方案之前使用

在实现任何功能或修复 bug 时、编写实现代码之前使用

对整个代码库做质量审计:bug、安全、真实负载、缺失的测试、性能,以及该删的内容。按重要性排序。

把所有 ponytail: 快捷注释汇总成一份技术债清单,让欠下的账被跟踪而不是被遗忘。一次性报告。

以记分板形式展示 ponytail 的实测收益:代码更少、成本更低、速度更快,数据来自 agent 基准测试平均值。一次性展示。

ponytail 模式、技能和命令的快速参考。一次性展示。

对 diff 做质量审查:bug、安全、真实负载、缺失的测试、性能,以及该删的内容。每条发现都说明会出什么问题、怎么修。

面向任何编码任务的"懒资深开发者"模式:用最小的改动彻底解决问题,回复让忙碌的人一遍就能看懂。

超高压缩沟通模式。用原始人式说话方式省约 75% token,同时保证技术准确性。支持强度等级:lite、full(默认)、ultra、wenyan-lite、wenyan-full、wenyan-ultra。当用户说 "caveman mode"、"像原始人一样说话"、"少用 token"、"简洁点",或调用 /caveman 时使用。要求节省 token 时也会自动触发。

对整个代码库做质量审计:bug、安全漏洞、真实负载下会崩的地方、无测试覆盖的高风险代码、性能瓶颈,以及该删、该合并、该拆分的部分。按优先级排序,每条发现都用大白话解释。只读报告,不改动任何代码。用于 "审计这个代码库"、"review 整个仓库"、"找出冗余"、"哪些能删"、/ponytail-audit。

把所有 `ponytail:` 快捷注释列成一份技术债清单。只读报告,不改动任何代码。用于 "ponytail 债务"、"ponytail 欠了什么"、"列出捷径"、/ponytail-debt。

展示 ponytail 基准测试的实测收益(代码、成本、速度)。一次性展示。用于 /ponytail-gain、"ponytail 能省什么"、"ponytail 影响"。

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.

Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.

Guides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need to figure out what broke and why — a systematic approach to finding and fixing the root cause rather than guessing.

Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch. Use when asked to review a diff or a pull request, even when the diff is pasted inline.

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.