statusbar-doctor
CommandRun cs doctor to diagnose why the status bar isn't showing what you expect
Switch the status-bar look (aurora blocks / aurora thin / classic)
> /plugin marketplace add leeguooooo/claude-code-usage-bar> /plugin install claude-statusbar@claude-statusbar
description: Switch the status-bar look (aurora blocks / aurora thin / classic) argument-hint: <block|thin|classic> allowed-tools: ["Bash"]
Argument: `$ARGUMENTS`
There are three looks:
| Look | Commands | |---|---| | `block` — aurora with ■ bars (default) | `cs config set style aurora && cs config set bar_glyph block` | | `thin` — aurora with a thin ━ line | `cs config set style aurora && cs config set bar_glyph thin` | | `classic` — the original battery bar | `cs config set style classic` |
Steps:
1. If `$ARGUMENTS` is empty, run `cs preview` to show all three and ask the user to pick. 2. Otherwise run the commands for that look from the table above. 3. Render a one-line preview from cached real data so the user sees the result:
cat ~/.cache/claude-statusbar/last_stdin.json | cs
If the cache file does not exist, skip this step — no Claude Code session has populated it yet. 4. Tell the user the change is persistent for all future Claude Code sessions.
If `$ARGUMENTS` is not `block`, `thin` or `classic`, list the three looks and ask which one they meant.
Your Claude Code usage, at a glance. 5h / 7d rate-limit bars, reset countdowns, model, context window, and prompt-cache freshness — inline in Claude Code's status line. Claude Code tells you almost nothing about where you stand against your rate limits.
Run cs doctor to diagnose why the status bar isn't showing what you expect
Render the three status-bar looks using your real cached data
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.