원클릭으로
statusline-setup
Configure Claude Code's statusLine to call `steop statusline`
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Configure Claude Code's statusLine to call `steop statusline`
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Clarify phase of the workflow chain. Uses Opus to analyze the user's request, resolve ambiguities, define scope, and produce a clear task brief before research begins.
Execute phase of the workflow chain. Uses Haiku (simple), Sonnet (standard), or Opus (complex) to implement code changes according to a plan. Use when the user has an approved plan ready to execute.
Flow workflow chain that runs clarify → [research] → plan → execute → validate end-to-end without stopping. Pauses only on genuine ambiguity or circuit-breaker conditions.
Plan phase of the workflow chain. Uses Opus to design an implementation strategy. Use when the user wants to create a detailed plan before executing changes.
Research phase of the workflow chain. Uses Haiku (simple) or Sonnet (standard) to research the codebase and gather context for a task. Use when the user wants to investigate code before planning.
Validate phase of the workflow chain. Uses Sonnet to review and validate implementation changes. Use when the user wants to validate that code changes are correct and complete.
| name | statusline-setup |
| description | Configure Claude Code's statusLine to call `steop statusline` |
| user-invocable | true |
Optional companion to /steop:install. Wires the two-line statusline into Claude Code's native status bar by patching ~/.claude/settings.json to invoke steop statusline directly — no shell script, no jq prerequisite.
What gets rendered:
steop binary itself)steop: [mode] phase step loop=N tools=N retries=N), or idle/offline when unavailableRequires /steop:install to have been run first so steop is on PATH.
which steop && steop version
If steop is not found, run /steop:install first and ensure ~/.local/bin is on your PATH.
~/.claude/settings.jsonpython3 - <<'PY'
import json, pathlib, shutil, sys
p = pathlib.Path.home() / ".claude" / "settings.json"
p.parent.mkdir(parents=True, exist_ok=True)
data = {}
if p.exists() and p.read_text().strip():
try:
data = json.loads(p.read_text())
except json.JSONDecodeError as e:
print(f"error: existing {p} is not valid JSON: {e}", file=sys.stderr)
sys.exit(1)
desired = {
"type": "command",
"command": "steop statusline",
}
prev = data.get("statusLine")
if prev == desired:
print(f"{p} already configured — nothing to do")
sys.exit(0)
if prev:
if p.exists():
shutil.copy(p, p.with_suffix(".json.bak"))
print(f"backed up existing settings to {p.with_suffix('.json.bak')}")
print(f"warning: replacing existing statusLine: {prev}", file=sys.stderr)
data["statusLine"] = desired
p.write_text(json.dumps(data, indent=2) + "\n")
print(f"wrote statusLine to {p}")
PY
If a different statusLine was already configured, the script prints a warning before overwriting and leaves settings.json.bak behind. Stop and ask the user whether to proceed if that happens.
Tell the user:
Restart Claude Code (quit and relaunch). The two-line statusline will appear at the bottom of your session on next launch. Run
/steop:st-flow <task>to see line 2 cycle throughclarify → research → plan → execute → validatewith the phase token colour-coded per the st-flow agent palette.
python3 - <<'PY'
import json, pathlib
p = pathlib.Path.home() / ".claude" / "settings.json"
if not p.exists():
raise SystemExit(0)
data = json.loads(p.read_text())
data.pop("statusLine", None)
p.write_text(json.dumps(data, indent=2) + "\n")
print("removed statusLine from settings.json")
PY
Then restart Claude Code.
steop binary on PATH (run /steop:install first).git is optional and only used for the branch segment at runtime.