bulwark-statusline
Skill8 starsChanged 5 months agoMITView on GitHub
Configure the Bulwark status line for Claude Code. Supports init, preset switching, and customization.
In this repository29 other files it gives its agents.
- anthropic-validatorSkill
- assertion-patternsSkill
- bug-magnet-dataSkill
- bulwark-brainstormSkill
- bulwark-researchSkill
- bulwark-scaffoldSkill
- bulwark-verifySkill
- code-reviewSkill
- component-patternsSkill
- continuous-feedbackSkill
- create-skillSkill
- create-subagentSkill
- fix-bugSkill
- governance-protocolSkill
- initSkill
- issue-debuggingSkill
- mock-detectionSkill
- pipeline-templatesSkill
- plan-creationSkill
- plan-to-tasksSkill
- product-ideationSkill
- session-handoffSkill
- setup-lspSkill
- spec-drift-checkSkill
- subagent-output-templatingSkill
- subagent-promptingSkill
- test-auditSkill
- test-classificationSkill
- test-fixture-creationSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Use this skill when:
- Distinctive: line 42
When invoked, you (Claude) execute the steps using the tools declared above (Bash, Read, Edit).
- Distinctive: line 75
Bash: Create config directory
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Bulwark Status Line
Configure the Bulwark multi-line status line for Claude Code.
When to Use
Use this skill when:
- Setting up the Bulwark status line for the first time (
init) - Switching between status line presets (
minimal,developer,cost) - User asks to configure or customize the status line display
Invocation
This skill can be invoked two ways:
| Method | Example |
| Command | /bulwark-statusline minimal |
| Conversational | "Change my status line to minimal" |
When invoked, you (Claude) execute the steps using the tools declared above (Bash, Read, Edit).
Usage
/bulwark-statusline init # Install with default (developer) preset
/bulwark-statusline minimal # Switch to minimal preset (1 line)
/bulwark-statusline developer # Switch to developer preset (3 lines)
/bulwark-statusline cost # Switch to cost preset (2 lines)Argument Handling
The subcommand is passed via $1:
/bulwark-statusline init
^^^^
$1 = "init"Parse $1 and execute the corresponding subcommand below.
Subcommand: init
Install the Bulwark status line for first-time setup.
Execute these steps:
- Bash: Create config directory
mkdir -p ~/.bulwark - Bash: Copy default config template
cp "${CLAUDE_PROJECT_DIR}/skills/bulwark-statusline/templates/statusline-default.yaml" ~/.bulwark/statusline.yaml - Spawn statusline-setup agent to update settings.json:
Task(subagent_type="statusline-setup", prompt=" GOAL: Add statusLine configuration to .claude/settings.json TARGET: .claude/settings.json (project level) EXACT JSON to add at top level of settings.json: { \"statusLine\": { \"type\": \"command\", \"command\": \"${CLAUDE_PROJECT_DIR}/skills/bulwark-statusline/scripts/statusline.sh\" } } If .claude/settings.json does not exist, create it with just this content. If it exists, merge the statusLine key into the existing JSON, preserving all other keys. ") - Display to user: "Status line installed. Restart session to activate."
Subcommand: minimal
Switch to minimal preset (single line: model + gauge + tokens).
Execute these steps:
- Read:
~/.bulwark/statusline.yaml - Edit: Change
preset:value tominimal - Display to user: "Switched to minimal preset."
Subcommand: developer
Switch to developer preset (3 lines).
Lines displayed:
- Line 1: Model + gauge + tokens
- Line 2: Last modified file
- Line 3: Git branch + pending count
Execute these steps:
- Read:
~/.bulwark/statusline.yaml - Edit: Change
preset:value todeveloper - Display to user: "Switched to developer preset."
Subcommand: cost
Switch to cost preset (2 lines).
Lines displayed:
- Line 1: Model + gauge + tokens + cost
- Line 2: Duration
Execute these steps:
- Read:
~/.bulwark/statusline.yaml - Edit: Change
preset:value tocost - Display to user: "Switched to cost preset."
File Locations
| File | Purpose |
~/.bulwark/statusline.yaml | User config (presets, colors) |
skills/bulwark-statusline/scripts/statusline.sh | Main script (bundled with skill) |
skills/bulwark-statusline/templates/statusline-default.yaml | Default config template |
Notes
- Status line updates automatically on each interaction
- Multi-line output is supported
- Colors use RGB escape codes for exact hex values
- Gauge and percentage colors match threshold (green/yellow/coral)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

