ponytail-help
Quick reference for ponytail levels, skills and commands. One-shot display. Use for /ponytail-help, "ponytail help", "how do I use ponytail".
- 0
- Installs
- —
- Rating
- —
- Success rate
- 1
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 213ff356407b2a4d… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
Ponytail Help
Display this reference card when invoked. One-shot, do NOT change mode, write flag files, or persist anything.
Levels
| Level | Trigger | What change |
|---|---|---|
| Lite | /ponytail lite | Build what was asked, name the smaller option in one line. |
| Full | /ponytail | The smallest complete change, a check where the logic needs one, and a reply that names what was skipped and any risk. Default. |
| Ultra | /ponytail ultra | Also questions the request and pushes back before building. |
Level sticks until changed or session end.
Skills
| Skill | Trigger | What it does |
|---|---|---|
| ponytail | /ponytail | Lazy mode itself: least new code, clear replies that name skipped work and risks. |
| ponytail-review | /ponytail-review | Quality review of a diff: bugs, security, load, missing tests, speed, what to cut. Each finding says what goes wrong and how to fix it. |
| ponytail-audit | /ponytail-audit | The same quality review for the whole repo, ranked. |
| ponytail-debt | /ponytail-debt | Harvest shortcut: comments into a tracked ledger. |
| ponytail-gain | /ponytail-gain | Measured-impact scoreboard: less code, less cost, more speed. |
| ponytail-help | /ponytail-help | This card. |
In Codex CLI and the IDE extension, invoke skills with $ponytail:ponytail,
$ponytail:ponytail-review, or $ponytail:ponytail-help. Claude Code and OpenCode use the
slash-command forms above (OpenCode ships all six as slash commands).
Deactivate
Say "stop ponytail" or "normal mode". Resume anytime with /ponytail.
/ponytail off also works.
Configure Default Mode
Default mode = full, auto-active every session. Change it:
Environment variable (highest priority):
export PONYTAIL_DEFAULT_MODE=ultra
Config file (~/.config/ponytail/config.json, Windows: %APPDATA%\ponytail\config.json):
{ "defaultMode": "lite" }
Set "off" to disable auto-activation on session start, activate manually
with /ponytail when wanted.
Resolution: env var > config file > full.
Update
Enable auto-update once: open /plugin, go to Marketplaces, pick ponytail, Enable auto-update. Claude Code then pulls new versions at startup (run /reload-plugins when it prompts). Manual refresh: /plugin marketplace update ponytail then /reload-plugins.
If /plugin is not recognized, your Claude Code is out of date. Update it (npm install -g @anthropic-ai/claude-code@latest, or brew upgrade claude-code) and restart. Other hosts use their own update flow.
More
Full docs + examples: https://github.com/DietrichGebert/ponytail
Files
1- SKILL.md
2927276bc92.8 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from DietrichGebert/ponytail5
Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains abo
Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split. Ranked, each finding explained in plain English. One-shot report, changes nothing. Use for "audit this codebase", "review the whole repo", "find
List every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.
Show ponytail's measured savings (code, cost, speed) from the benchmark. One-shot display. Use for /ponytail-gain, "what does ponytail save", "ponytail impact".
Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last