メニュー
Whole-repo audit for over-engineering — ranked delete/simplify list (repo-wide ponytail-review). Use for "audit this codebase", "find bloat", "ponytail-audit", "/ponytail-audit". Read-only; does not apply fixes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ponytail-audit |
| description | Whole-repo audit for over-engineering — ranked delete/simplify list (repo-wide ponytail-review). Use for "audit this codebase", "find bloat", "ponytail-audit", "/ponytail-audit". Read-only; does not apply fixes. |
On-demand loading: Read when the user wants a repo-wide complexity audit, not a diff review.
Activation: Over-engineering and complexity only. Correctness, security, and performance are out of scope — route to
code-reviewer,security-auditor, ordifferential-review.
Adapted from ponytail-audit (MIT).
delete: — dead code, unused flexibility, speculative featurestdlib: — hand-rolled thing the stdlib shipsnative: — dependency duplicating platform featuresyagni: — abstraction with one implementationshrink: — same logic, fewer linesnode_modules, .git, dist, build, .cursor/plans, lockfiles).path: tag: finding. replacement.net: -N lines, -M deps possible. or Lean already. Ship.Read-only — lists findings, applies nothing unless user asks to fix.
Orchestrate continual learning by delegating transcript mining and AGENTS.md updates to the knowledge-synthesizer subagent. Use when asked to mine prior chats, maintain AGENTS.md, update learned preferences, or run the continual-learning loop.
Security-focused review of code diffs and PRs with surface classification and Semgrep on changed files. Use when reviewing pull requests, branch diffs, or validating security regressions before merge.
Live Notion session log (L4b) — create, incremental updates during work, finalize on CLOSE. Works on any Cursor project workspace.
Bootstrap a new project with Cursor-ready configuration: AGENTS.md, per-project .cursor/rules/project-conventions.mdc, and optional memory_bank/ scaffold. Use at project initialization, when starting a new repo, or when the user says "set up Cursor for this project" / "bootstrap this project" / "init project config".
Phase-1 repo reconnaissance as a standalone skill: stack detection, relevant files, validation commands from repo evidence, workflow hints, and risk flags. Use inside /scout, /ks-conductor pre-flight, or any read-only discovery before planning or implementation.
Validates phase outputs before advancing the SDLC. Defines expected artifacts per phase (intake, scout, plan, critic, build, test, review, document, close) and produces a clear PASS / CONDITIONAL / BLOCK verdict with gaps. Use at orchestrator or command phase boundaries, before expensive work, or when the user asks to verify a gate or "are we ready to proceed".