memex tree

What it does

Lists the folders and files below the root, or below a path you name, two levels down by default. Each folder line carries its README’s one-liner and, across its whole subtree, how many files should have a header and how many of those lack one; each file line carries its header’s one-liner. It is the orientation that would otherwise take a show per folder, and like info it prints one-liners, never bodies.

A folder with files but no README reads (no README), and a file that should have a header and has none reads (no header); the fix for each follows the list. A folder of data alone gets no placeholder. Every label is a valid show ref.

Flags

<path>

A folder or a file to start from; with none, the root. A label, a bare id or a glob is not a path.

--depth N

How many levels to list, 1 or more (default 2). A folder at the last level still counts its whole subtree.

--limit N

Caps the entries printed (default 200).

--json

One JSON document: the scope, its counts and the entries.

One folder

$ memex tree supabase
tree  supabase · 11 files · 2 no header  (showing 6 of 6)
  supabase/functions/  Owns the Edge Functions folder: one Deno function per subfolder.  (10 files · 2 no header)
    supabase/functions/_shared/  Code the functions import.  (6 files)
    supabase/functions/billing/  (no README)  (4 files · 2 no header)
    supabase/functions/deno.json
  supabase/migrations/  Schema changes, oldest first.
  supabase/seed.ts  Seeds a local database with test users.
(no README): add README.md here; line 1 is # Name, then a paragraph saying what the folder is