setup-statusline

Automate Codex statusline customization to display context usage, git branch, and PR counters.

26|2|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/sburl/CrossCheck --skill setup-statusline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-statusline
Source: https://github.com/sburl/CrossCheck/tree/main/codex/skills/setup-statusline
Command: npx skills add https://github.com/sburl/CrossCheck --skill setup-statusline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codex users often lose track of context usage and the current git branch across sessions. This skill provides a streamlined approach to customize the statusline so essential information stays visible, reducing context-switching friction and mistakes.

Core Features & Use Cases

  • Show context usage percentage, current git branch, optional PR counter, and worktree name.
  • Offer configurable format strings to tailor what appears in the statusline.
  • Support multi-worktree workflows with quick visual differentiation for each Codex session.

Quick Start

Configure a global statusline format to display context usage and the current git branch across all Codex sessions.

Frequently Asked Questions about setup-statusline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I customize the Codex statusline to show git branch and context usage?

You can customize the Codex statusline by defining configurable format strings that display context usage percentage, current git branch, optional PR counter, and worktree name for quick visual assessment during development.

Can I apply a consistent statusline format across multiple Codex worktree sessions?

Yes, the statusline customization applies across multi-worktree Codex sessions to ensure consistent visibility, allowing quick context assessment and branch identification for each active session.

What is the best way to display PR counters and worktree names in my terminal statusline?

The best way to display PR counters and worktree names is by configuring optional statusline integrations with format rules and color-coding to visually differentiate each Codex session.

Does customizing the Codex statusline require any external dependencies or components?

No external dependencies or components are required to customize the Codex statusline, as the skill validates safety constraints and prevents script-level risks internally.

Why do I lose track of my current git branch when switching between multiple terminal sessions?

You lose track because essential context and branch information are not visible by default, but customizing the statusline reduces context-switching friction and mistakes by keeping critical data visible.

Are there limitations when defining color-coding and format rules for the Codex statusline?

The customization supports defining format rules and color-coding while validating safety constraints and preventing script-level risks, ensuring secure statusline modifications across sessions.