Best use case
statusline is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Configure the devloop statusline for Claude Code
Teams using statusline should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/statusline/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How statusline Compares
| Feature / Agent | statusline | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Configure the devloop statusline for Claude Code
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Devloop Statusline Setup
Configure the devloop statusline to display real-time session information.
## What the Statusline Shows
- **Model**: Current model name (Opus/Sonnet/Haiku)
- **Context**: Progress bar + percentage of context window used
- **Tokens**: Total session tokens (formatted as K/M)
- **Path**: Current working directory (shortened)
- **Git Branch**: Current branch name
- **Plan Progress**: Tasks completed (X/Y) from `.devloop/plan.md`
## Step 1: Read Current Settings
Read the user's Claude Code settings:
```
Read ~/.claude/settings.json
```
## Step 2: Check Current Status
Analyze the settings to determine the current state:
1. **No statusLine field**: Safe to configure
2. **Existing devloop statusline**: May need path update
3. **Other statusline**: Ask user what to do
## Step 3: Get Plugin Path
The devloop statusline script path follows this pattern:
`~/.claude/plugins/cache/cc-plugins/devloop/{version}/statusline/devloop-statusline.sh`
Find the installed version by checking the plugin cache directory.
## Step 4: Handle Based on State
### If no statusline configured:
Add the statusLine field to settings.json:
```json
{
"statusLine": {
"type": "command",
"command": "~/.claude/plugins/cache/cc-plugins/devloop/{version}/statusline/devloop-statusline.sh",
"padding": 0
}
}
```
### If existing devloop statusline:
Check if path needs updating (version change). Update if necessary.
### If other statusline configured:
```yaml
AskUserQuestion:
questions:
- question: "You have an existing statusline configured. What would you like to do?"
header: "Statusline"
multiSelect: false
options:
- label: "Replace with devloop"
description: "Use devloop statusline instead"
- label: "Keep existing"
description: "Don't change current statusline"
```
## Step 5: Apply Configuration
Use the Edit tool to update `~/.claude/settings.json` with the statusLine configuration.
## Step 6: Confirm
Tell the user:
- Statusline has been configured
- Restart Claude Code to see the changes
- The statusline shows: Model, Context %, Tokens, Path, Git branch, Plan progress
## Dependencies
The statusline requires `jq` for JSON parsing. If not installed:
- macOS: `brew install jq`
- Ubuntu/Debian: `sudo apt install jq`
- Windows: `choco install jq`
## Troubleshooting
If the statusline doesn't appear after restart:
1. Verify jq is installed: `which jq`
2. Check settings.json is valid JSON
3. Ensure the script path exists and is executable
4. Try running the script manually to test
## Customization
To customize the statusline:
1. Copy the script: `cp ~/.claude/plugins/cache/cc-plugins/devloop/*/statusline/devloop-statusline.sh ~/.claude/statusline.sh`
2. Edit `~/.claude/statusline.sh` to your preferences
3. Update settings.json to point to your custom scriptRelated Skills
Example Skill
Brief description of what this skill does and the domain expertise it provides.
vulnerability-patterns
Index of vulnerability detection pattern skills. Routes to core patterns (universal) and language-specific patterns for security scanning.
vuln-patterns-languages
Language-specific vulnerability detection patterns for JavaScript/TypeScript, Python, Go, Java, Ruby, and PHP. Provides regex patterns and grep commands for common security vulnerabilities.
vuln-patterns-core
Universal vulnerability detection patterns applicable across all programming languages. Includes hardcoded secrets, SQL/command injection, path traversal, and configuration file patterns.
scan
Run a security assessment using deterministic static analysis tools with LLM-powered triage
results
View the most recent security scan results without re-running the scan
remediation-library
Index of security remediation skills. Routes to specialized skills for injection, cryptography, authentication, and configuration vulnerabilities.
remediation-injection
Security fix patterns for injection vulnerabilities (SQL, Command, XSS). Provides language-specific code examples showing vulnerable and secure implementations.
remediation-crypto
Security fix patterns for cryptographic vulnerabilities (weak algorithms, insecure randomness, TLS issues). Provides language-specific secure implementations.
remediation-config
Security fix patterns for configuration and deployment vulnerabilities (path traversal, debug mode, security headers). Provides language-specific secure implementations.
remediation-auth
Security fix patterns for authentication and authorization vulnerabilities (credentials, JWT, deserialization, access control). Provides language-specific secure implementations.
fix
Fix or guide remediation for a specific security finding from the latest scan report