# /ponytail: Have your agent write the least new code that works

Source: https://trendhub.net/skills/dietrichgebert-ponytail/ponytail
Skill folder: https://github.com/DietrichGebert/ponytail/tree/main/skills/ponytail
Pack: Ponytail (https://trendhub.net/skills/dietrichgebert-ponytail)
Works with: Claude Code, Codex

The core Ponytail skill stays on for the whole session and changes how the agent picks a solution. It first maps every place a change must reach, then works down a ladder from not building at all to reusing repo code, standard library, installed packages and one-liners, writing new code only last. Risky logic still gets a test and safety is never trimmed.

## When to use it

- Your agent keeps adding libraries, wrappers or options you did not ask for.
- You want a vague request like build me X turned into its smallest useful version.
- You are fixing a bug and want the root cause fixed once in shared code.

## How it works

1. **Scope the change**: The agent reads the task and touched code and lists callers, tests, fixtures, config and exports the change must reach, plus what it could break for users.
2. **Climb the ladder**: It stops at the first option that works: skip it, reuse a repo helper, use the standard library or platform, use an installed dependency, write one line, or write the minimum.
3. **Finish everything**: It updates every caller, test and fixture the change breaks and keeps error handling when moving code.
4. **Leave a check**: New logic with branches, loops, parsing, money or security gets one small test or self-check, and known limits get a shortcut: comment.
5. **Report risks**: Each reply closes with a line or two on what was skipped or unchecked and any risk you should know.

## What it steers the agent away from

- Adding a dependency to save a few lines
- Abstractions, config or code kept for later that nobody requested
- Cutting validation, data-loss handling, security or accessibility to shrink a diff

## What it can touch

Reads and edits project files and runs searches such as grep for callers; it works like a normal coding session with a different set of rules.

## Pairs well with

- `/ponytail-debt`
- `/ponytail-review`

## Questions

### Can I make it less or more strict?

Yes. Lite builds what you asked and only mentions a smaller option, full is the default, and ultra also pushes back on parts of the request before building.

### How do I turn it off?

Say stop ponytail or normal mode, or run /ponytail off; /ponytail turns it back on.
