Skip to content

Swipe right for a newer agent, Automation Recipe Writer. Swipe left for an older agent, Error Message Poet.

Issue 22 · 26 Sep 2026 · Easy · Free

CLI Help Rewriter

The help text lists forty flags in alphabetical order, and the one command a person needs to copy is not among them.

Paste --help output. Get three copy-paste examples, the flags that matter, and the ones that should stay hidden.

Category
Dev Tools
Runs in
ChatGPT
Claude
Gemini

What you put in and what you get out

Sample you can paste

$ ledger --help
Usage: ledger <command> [flags]
Commands:
  refund     Refund an order
  review     Weekly review from a dump
Flags:
  --help
  --version
  --json
  --config string
  --timeout duration (default 30s)
  --dry-run
  --endpoint string
  --verbose
  --no-color
  --experimental-split
I want examples for refund. A refund needs --order and an optional --dry-run.
--experimental-split is unfinished. Do not feature it.
The real binary name is ledger.

Share this agent

CLI Help Rewriter — You put in $ ledger --help. You get out Hidden. Free from One Agent a Day.

Share on XShare on LinkedIn

30-second demo

0:00

The dump

ledger refund needs --order, optional --dry-run. A long flag list includes --experimental-split, which they said is unfinished.

How it works

Help text is a dictionary. People need a sentence they can paste. You give it the help for one command and the example you wish it had led with. It returns three examples using only flags from the paste, then a short list of the flags that belong in those examples.

Unfinished flags stay out. The rewriter does not invent a subcommand or a default you did not show. The binary name is the one you typed.

Put the examples above the flag list. If a dry run exists, run it. A documented command that fails on a clean machine is worse than a short help text.

Use it

  1. Step 1

    Paste one command's help

    Copy the usage block for the command you care about, not the entire manual for a huge CLI. Add one line about which example a new user needs.

  2. Step 2

    Mark unfinished flags

    Name any flag that should stay out of the examples. The rewriter will not advertise it.

  3. Step 3

    Paste the prompt

    You get three examples a person can copy, a short list of flags that matter, and the flags you hid.

  4. Step 4

    Replace the examples in the help or the README

    Put the examples above the flag dictionary. Run one of them with --dry-run if that flag exists, so the docs are not fiction.

Prompt

cli-help-rewriter.prompt.txt

You rewrite CLI help into examples a person will copy. You do not invent flags.

INPUTS
- Help text for one command.
- The example they want a new user to run.
- Flags that must not be featured.

RULES
- Three examples, copy-pasteable, using the binary and command from the help text.
- Every flag in an example must appear in the help text.
- Do not feature a flag they banned.
- If a required flag is obvious from the help, the first example includes it.
- Do not invent a default, a subcommand, or an example that needs a secret. Use placeholders like ORDER_ID.
- After the examples, list "flags that matter" (the ones you used) and "leave in the dictionary" (the rest).
- If the help is too broad (many unrelated commands), ask them to paste one command and stop.

OUTPUT
## Examples
Three fenced commands, each with a one-line caption.

## Flags that matter
## Leave in the dictionary
## Not featured
Banned flags, or "None."
Was this useful?

A yes or no is enough. The note stays on this server's log.

Swipe sideways

  1. Dev Tools7 Oct 2026 · #33API Error ExplainerPaste a status code and the response body. Get what broke, what to change in the request, and whether a retry will help.InRequest I sent: POST /api/refundsOutRetryMedium
    Preview this drop
    1. 0:00 The callPOST /api/refunds returned 401 bad signature twice. The body says the prefix should be sha256=. They may have signed with the example placeholder.
    2. 0:08 What brokeThe server rejected the signature. The status is not a transient outage. The prefix note is a hint about the header format.
    3. 0:16 The changeSign the raw body with the real secret, prefix the header with sha256=, and keep the same idempotency key so a later success does not double-apply.
    4. 0:24 RetryDo not retry the same bytes. Retry once after the header changes. Forging a signature for someone else's API is out of scope.

    No daily video for this drop yet. The in and out lines above are the preview.

  2. Dev Tools14 Sep 2026 · #10README DoctorPaste a README. Get a rewrite a new contributor can follow: install, run, test, and the command that proves it worked.In# LedgerOutThe proofEasy
    Preview this drop
    1. 0:00 The old READMEA welcome, a Slack shrug, and scripts named dev, test, and check. No .env.example in the paste.
    2. 0:08 The rewriteInstall, copy env, run dev, run test. DATABASE_URL is named because the paste named it.
    3. 0:16 The holeNot in the README: which database, and the contents of .env.example. The doctor does not invent Postgres.
    4. 0:24 The proofThe command to prove it is npm test, because that script exists. Slack is not a setup step.

    No daily video for this drop yet. The in and out lines above are the preview.

  3. Coding & Vibe Coding15 Oct 2026 · #41Session HandoffPaste the mess from a coding session. Get a handoff note: what shipped, what is broken, and the exact prompt to paste tomorrow.InBranch: feat/billing-uiOutTomorrow's first promptEasy
    Preview this drop
    1. 0:00 The swampBranch feat/billing-ui. Auth works. Billing page half done. Stripe webhook returns 400. Receipt email never fires.
    2. 0:08 What actually shippedLogin on staging, pricing table render, stripe package installed. Plan change is still a stub. PayPal left alone on purpose.
    3. 0:16 What is brokenWebhook 400, missing signature check, BillingForm customerId null, receipt email not wired. Ranked by what blocks the rest.
    4. 0:24 Tomorrow's first promptA paste-ready prompt that starts at the webhook 400, forbids touching PayPal, and asks for a signature check plus a failing test.

    No daily video for this drop yet. The in and out lines above are the preview.

Tomorrow's drop

Get tomorrow's agent in your inbox

One email when the drop goes up. No digest, no course. Unsubscribe whenever the provider lets you.

Pro and custom

€9/month when Pro opens

Early look at the next drop, a better archive, and the occasional agent that does not fit the public mix. The daily agent stays free. A custom build is €49–199. Nothing is charged from this form.

Join the Pro waitlist

Tomorrow's drop

Get the daily agent

One email when the drop goes up. The same list as the signup on the page.