LedgerHQ/lumen / .claude/skills/lumen-consumer-upgrade
lumen-consumer-upgrade
VerifiedUpgrade a consumer repo to the latest Lumen: audit the gap, bump every `@ledgerhq/lumen-*` package, apply each migration crossed, verify, and open the PR. Run from the consumer repo's root, only when asked to upgrade or audit Lumen there.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.7 KB |
| references/audit-template.md | markdown | 1.2 KB |
| references/breaking-changes.md | markdown | 21.0 KB |
| references/pr-template.md | markdown | 817 B |
| scripts/lumen-api-diff.mjs | script | 8.0 KB |
references/audit-template.md
View on GitHub# Audit template
Fill in every section, even when empty ("none"). Keep it factual: hits with
`file:line`, no fixes yet.
```markdown
# Lumen audit: <repo>
## Versions
| Package | Installed (lockfile) | Target | Releases behind |
|---|---|---|---|
Tailwind: <version> · Package manager: <npm|pnpm|yarn> · Workspaces: <paths>
## Blockers
<rows whose fix says Stop, Lumen packages the catalog doesn't know, anything else that stops the upgrade. "None" otherwise.>
## Breaking changes crossed
| Row | Hits | Where (file:line, first 5) | Effort |
|---|---|---|---|
<every selected catalog row, hits = 0 included>
Skipped (already past their version): <ids>
## Uncatalogued (from the API diff)
<removed exports, tokens or classes the app uses that no catalog row explains: name, file:line, package version range>
## Judgment calls needed
<one bullet per ⚖️ hit: the call site, the options, the catalog default>
## Replacements (♻️)
| Row | Local version (file) | Safe to replace? (the row's check) | Plan |
|---|---|---|---|
## Visual review list
<screens or components hit by 👁 rows>
## Out of scope (follow-ups)
<findings outside the upgrade, Lumen packages to adopt, Lumen gaps…>
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |