app_tagline_backfill

App Tagline Backfill

Apps created before tagline existed share a card with an empty description. This skill adds one sentence to each such app, commits it, and reinstalls so the card is redrawn. It edits nothing else.

Modes

• AUTO — the caller (the coding app's agent-turn-finished hook) hands you the absolute source roots to process. Nobody is watching: skip the confirmation step, process every listed app, and finish with the report.
• MANUAL — the guardian asked. Discover the apps yourself (step 1), show the draft table (step 3), and write only after they approve or edit it.

Step 1: Discover (MANUAL only)

LOCK="$HOME/.rome/${ROME_PROFILE:-default}/apps.lock.json"
node -e '
  const lock = JSON.parse(require("fs").readFileSync(process.argv[1], "utf8"));
  for (const [id, e] of Object.entries(lock.apps)) {
    if (e.source?.mode === "source" && e.enabled && e.state === "installed") console.log(id, e.source.path);
  }
' "$LOCK"

For each printed root, an app qualifies when <root>/app.yaml has a web: block and no tagline: line:

grep -q '^web:' "$ROOT/app.yaml" && ! grep -q '^tagline:' "$ROOT/app.yaml" && echo "$ROOT"

Skip everything else and say why in the report: appstore entries (read-only bundles, the author owns them), first-party apps (shipped with Rome, already done), apps without web: (no card), apps that already have a tagline.

Step 2: Draft one sentence per app

Read name, description, and README.md (if present) under the root. Write the tagline by the same rule app_creation/REFERENCE.md gives:

• One sentence, at most 80 characters (40 for CJK). No line breaks, no double quotes.
• Lead with what the user gets. No implementation details, jargon, or acronyms. Read it like an App Store subtitle.
• Do not copy description — it is written for agents, not people.

Good: Track every mortgage rate that matters to you, updated daily. Bad: A cron-driven scraper that stores rates in SQLite. (mechanism, not benefit) Bad: Mortgage Monitor (a name, not a sentence)