LedgerHQ/lumen / .claude/skills/lumen-adoption-report
lumen-adoption-report
VerifiedUse when asked to check Lumen version adoption across consumer repos, generate the Lumen adoption report, or find which repos are behind on a Lumen package version, or who owns those repos.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.6 KB |
SKILL.md
View on GitHub---
name: lumen-adoption-report
description: >-
Use when asked to check Lumen version adoption across consumer repos,
generate the Lumen adoption report, or find which repos are behind on a
Lumen package version, or who owns those repos.
---
# Lumen adoption report
```bash
npx nx run adoption-tool:report # full markdown table (GitHub/PR/terminal)
npx nx run adoption-tool:report-summary # Slack-ready bulleted summary instead
npx nx run adoption-tool:report-json # machine-readable snapshot (also always written to report.json)
npx nx run adoption-tool:owners # maps each consumer repo to its catalog team / code owners (readable summary)
npx nx run adoption-tool:discover # diffs data/consumers.json against a fresh code search, never writes it
```
Reports cover `production` consumers only. Append `--status internal-tool`
or `--status all` when the user asks about internal tools or every consumer.
Logic and details live in
[internals/adoption-tool](../../../internals/adoption-tool) — read its
README and source rather than duplicating them here. Use `report` for a full
table, `report-summary` for Slack — present whichever one printed as-is,
don't reformat it yourself. A non-zero exit means some repos couldn't be
read (shown as `unresolved`) — say so rather than presenting the table as
complete. For a repo `discover` finds, hand-edit
`internals/adoption-tool/data/consumers.json` (with its `status`) if it is a
real consumer, or `internals/adoption-tool/data/ignored-repos.json` (with a
`reason`) if it is a prototype or experiment.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList 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. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |