statusline-config
StatusLine Config
Customize ~/.claude/statusline-command.sh — segments, themes, and colors.
When NOT to Use
| Scenario | Use Instead |
|---|---|
| Setting statusline for the first time (no customization needed) | Built-in statusline-setup agent (Claude Code agent type) — applies defaults automatically |
Editing settings.json directly |
Manual edit — this skill manages statusline-command.sh, not settings.json |
| Debugging Claude Code startup issues | /claude-health — config health check |
Segments
| Segment | JSON Field | Default | Notes |
|---|---|---|---|
| Directory | workspace.current_dir |
ON | Truncate deep paths: ~/.../last-dir |
| Git branch | shell git |
ON | --no-optional-locks, cache 5s |
| Agent | agent.name |
ON (conditional) | Show when present; color: C_MODEL |
More from sd0xdev/sd0x-dev-flow
tech-spec
Tech spec generation and review. Use when: designing features, writing specs, spec review. Not for: requirements analysis (use req-analyze), implementation (use feature-dev), architecture advice (use codex-architect). Output: numbered tech spec document.
47codex-brainstorm
Adversarial brainstorming via Claude+Codex debate. Use when: exploring solutions, feasibility analysis, exhaustive enumeration. Not for: implementation (use feature-dev), architecture only (use codex-architect). Output: Nash equilibrium consensus + action items.
7security-review
Security review via Codex MCP. Use when: OWASP Top 10 audit, dependency vulnerability check, security-sensitive changes. Not for: code review (use codex-code-review), test review (use test-review). Output: security findings + audit report.
7test-review
Test coverage review via Codex MCP. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report.
7codex-code-review
Code review using Codex MCP. Use when: PR review, code audit, second opinion on changes. Not for: doc review (use doc-review), security audit (use security-review). Output: severity-grouped findings + merge gate.
7post-dev-test
Post-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests. Not for: unit test generation (use codex-test-gen), test review (use test-review). Output: test files + coverage report.
6