- Home
- Skills
- Charlesjones Dev
- Claude Code Plugins Dev
- Statusline Edit
statusline-edit_skill
26
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill charlesjones-dev/claude-code-plugins-dev --skill statusline-edit- SKILL.md3.6 KB
Overview
This skill edits an existing Claude Code status line configuration by launching a guided wizard with options pre-selected from the current script. It detects your platform, parses current SHOW_* settings, and updates only the configuration block so the rest of your script remains unchanged. The workflow enforces a no-argument invocation and stops if no status line script is present.
How this skill works
The skill first detects the OS and looks for the status line script in the standard location for Bash or PowerShell. If found, it reads the file and parses existing SHOW_* variables to determine default selections. It then runs a three-group wizard (Context, Project, Session) with multi-select options pre-populated from the parsed values and updates only the SHOW_* variable block in the original file. Finally, it prints a concise summary of the new configuration.
When to use it
- You already have a Claude Code status line script and want to tweak which elements are shown without rebuilding the script.
- You prefer a guided, pre-populated configuration flow that preserves all other script logic.
- You need to toggle visibility of model, token, project, or session indicators quickly.
- You want to maintain platform-specific script formats (Bash or PowerShell) while changing only variables.
Best practices
- Run the command with no trailing arguments; any provided text is ignored by design.
- Back up your existing status line script before running major edits, though the tool only replaces the configuration block.
- Verify the script path matches your OS: ~/.claude/statusline.sh for Mac/Linux, C:/Users/USERNAME/.claude/statusline.ps1 for Windows.
- Use the wizard selections to keep defaults and make minimal changes to avoid unintended formatting differences.
Example use cases
- Enable token count and progress bar while keeping model name and directory visible for verbose development sessions.
- Disable session cost display for privacy while leaving duration and time enabled for session tracking.
- Switch from showing Git branch to only showing the current directory for simpler status lines.
- Quickly reconfigure indicators when switching between local and remote development environments.
FAQ
The skill prints a message indicating the missing script and instructs you to run the statusline-wizard to set one up, then stops.
Will the skill rewrite my whole script?
No. It only replaces the SHOW_* variable block at the top of the existing script and preserves all other content.
Does the command accept arguments to pre-select options?
No. The command must be invoked without arguments; any trailing text is ignored by design.