文档生成
- 作者仓库星标 1,187
- 叉子 185
- 作者更新于 2026年6月14日 10:01
- 作者仓库 claude-code-skills
- 领域
- 通用
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @daymade · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- macOS · Linux
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- Shell 执行
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
---
name: statusline-generator
description: > A single-source-of-truth statusline for Claude Code. One script, two layouts, end-to-end self-…
category: 通用
runtime: 无特殊运行时
---
# statusline-generator 输出预览
## PART A: 任务判断
- 适用问题：通用任务拆解、检查和交付。
- 输入要求：目标材料、限制条件、期望输出和验收方式。
- 证据边界：围绕“Quick health check (start here when something is wrong) / Quick install / What you get”读取原文规则，不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断：确认你的需求是否属于通用任务拆解、检查和交付，并标出输入、限制和预期结果。
- **02** 执行计划：优先按“Quick health check (start here when something is wrong) / Quick install / What you get”拆成步骤，说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果：给出可复制的命令、文件改动、检查清单或内容草稿，并说明如何继续迭代。
- **04** 风险边界：结合 读取文件、写入/修改文件、执行终端命令、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件、执行终端命令；主要在本地完成；通常不需要额外 API Key。
- 先小样例验证，再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。原文出现了 `/tmp` 这类斜杠命令；如果你的 Agent 支持命令触发，优先用命令开场，再补充目标和边界。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是：读取文件、写入/修改文件、执行终端命令。
先用一个小任务确认它会围绕“Quick health check (start here when something is wrong) / Quick install / What you get”工作；涉及文件或命令时，先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作；如果输出泛泛而谈，就补充输入、边界和验收标准后重跑。
---
name: statusline-generator
description: > A single-source-of-truth statusline for Claude Code. One script, two layouts, end-to-end self-…
category: 通用
source: daymade/claude-code-skills
---
# statusline-generator
## 什么时候使用
- statusline-generator 是一个通用扩展技能，按 SKILL 适合处理通用任务拆解、检查、交付和复盘，核心价值是把输入、判断、执行、验证和交付边界固定下来，避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭…
- 面向通用任务拆解、检查和交付，优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Quick health check (start here when something is wrong) / Quick install / What you get」组织步骤，不把推断写成作者事实。
- 读取文件、写入/修改文件、执行终端命令；主要在本地完成；通常不需要额外 API Key。
- 先跑小样例，确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown，不编造命令、平台或依赖。作者原文负责流程事实；仓库文件负责来源和命令；流狐只补充适用场景、限制和质量判断。
skill "statusline-generator" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Quick health check (start here when something is wrong) / Quick install / What you get
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件、执行终端命令 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
}Statusline Generator
A single-source-of-truth statusline for Claude Code. One script, two layouts, end-to-end self-verification.
Quick health check (start here when something is wrong)
Run this first whenever the statusline misbehaves. It catches the silent failures that account for most "configured but not working" reports:
bash scripts/health_check.shIt validates four layers:
~/.claude/statusline.shexists and is executable. Missingchmod +xis the single most common silent-failure cause — Claude Code runs the script,execfails, statusline goes blank.~/.claude/settings.jsonhas a validstatusLineblock pointing at the script.- Mock stdin tests covering complete data, zero tokens, missing fields,
and
$HOMEpath shortening. - Real stdin replay from
/tmp/.claude-statusline-last-stdin.jsonif you previously ran withCLAUDE_STATUSLINE_DEBUG=1.
Each failure prints a one-line fix command — you don't have to read documentation to recover.
Quick install
bash scripts/install_statusline.shThis script:
- Backs up any existing
~/.claude/statusline.shandsettings.json. - Copies
generate_statusline.shto~/.claude/statusline.shandchmod +xs it. - Updates
settings.jsonstatusLineblock viajq(preserves other settings). - Mandatorily runs
health_check.shand shows the result — installation is not "complete" until verification passes.
Restart Claude Code (or send any new message) to see the statusline update.
What you get
Default — minimal one-line layout
~/code/myproject Opus 4.7 (1M context) ctx: 108K / 1MJust the essentials: short path, model name, absolute token counts. No colors, no git, no cost, no percentage. Designed for users who want signal without noise.
Full — multi-line with cost and git
Set CLAUDE_STATUSLINE_LAYOUT=full in your shell profile to enable:
alex (Sonnet 4.6) [$0.42/$25.93] ctx: 108K/1M (11%)
~/code/myproject
[git:main*+]- Line 1: user, model, ccusage session/daily costs, color-coded ctx (green ≤50%, yellow 51–80%, red >80%).
- Line 2: short path.
- Line 3: git branch with
*for modified,+for untracked.
Layouts: how to switch
The script reads layout from environment, not flags (Claude Code passes JSON on stdin,
so flags would conflict). Set in ~/.zshrc or ~/.bashrc:
# Minimal (default — same as not setting it)
export CLAUDE_STATUSLINE_LAYOUT=minimal
# Full
export CLAUDE_STATUSLINE_LAYOUT=fullRestart your shell (or source the rc file) so Claude Code inherits the change,
then send a message — statusline refreshes within 300ms.
Debug stdin capture
To see exactly what JSON Claude Code sends your script:
export CLAUDE_STATUSLINE_DEBUG=1Each invocation writes its stdin to /tmp/.claude-statusline-last-stdin.json
(overwriting on every refresh). Inspect with jq .. Useful for:
- Diagnosing why a field doesn't render the way you expect.
- Re-running the script against real input:
cat /tmp/.claude-statusline-last-stdin.json | ~/.claude/statusline.sh. - Filing bug reports — paste the dump as ground truth.
Authoring rules (why this skill is shaped this way)
Two production failure modes drove the current design. Both are sealed in code, not just docs:
Rule 1 — Always chmod +x, always verify by running
The single biggest silent-failure cause of any statusline is a script without
the executable bit: Claude Code's exec fails silently and the bar goes blank
with no error. install_statusline.sh always chmod +xs; health_check.sh
flags the bit if missing. If you hand-write or hand-edit a statusline script,
mock-test it before declaring done: echo '{}' | bash your-script.sh.
Rule 2 — "Configuration complete" is meaningless without evidence
"Wrote the file and updated settings.json" is not the same as "the script runs
and produces the expected output." install_statusline.sh therefore always
runs health_check.sh at the end and exits non-zero if any check fails.
Treat any "complete!" report from any agent that lacks evidence as suspect.
For field-level traps (used_percentage null at session start, total_input_tokens
semantics across Claude Code versions, hardcoded context_window_size), see
references/context-window-schema.md.
Customization
For colors, custom segments (hostname, time, etc.), and disabling cost tracking,
see references/customization.md.
Dependencies
The script auto-detects available tools and degrades gracefully:
| Tool | Required for | Fallback |
|---|---|---|
jq |
JSON parsing (preferred) | falls back to python3 |
python3 |
JSON parsing fallback | bare cwd only |
awk |
token K/M formatting | required by both layouts |
git |
git status (full layout) | silent skip if missing or not in repo |
ccusage |
cost (full layout) | silent skip if missing |
Install on macOS: brew install jq. On Debian/Ubuntu: apt install jq.
Troubleshooting
For symptom-by-symptom diagnostics, see
references/troubleshooting-decision-tree.md.
It walks through:
- Statusline blank or never updates (chmod cause)
- ctx segment missing or wrong (field traps)
- Want token counts not percentages (layout switch)
- Colors render as raw escape codes (terminal compatibility)
- Git segment missing (full layout)
- Cost segment missing (ccusage / cache)
- Edits have no effect (path mismatch)
- Slow refresh (jq vs python3)
Resources
| File | Purpose |
|---|---|
scripts/generate_statusline.sh |
The statusline script. Single source of truth. Two layouts via CLAUDE_STATUSLINE_LAYOUT. |
scripts/install_statusline.sh |
Idempotent installer. Backs up, copies, chmods, wires settings.json, runs health check. |
scripts/health_check.sh |
Four-layer verification: file perms, settings.json wiring, mock stdin tests, real stdin replay. |
references/troubleshooting-decision-tree.md |
Symptom-driven diagnostic flowchart. Load when statusline misbehaves. |
references/customization.md |
Color changes, custom segments, threshold tuning, single-line full layout. Load when user wants to modify how the statusline looks. |
references/context-window-schema.md |
Claude Code statusline JSON schema. Documents every field plus current_usage vs total_input_tokens semantics across versions. |
references/color_codes.md |
ANSI color codes reference. Load for color customization. |
references/ccusage_integration.md |
ccusage integration deep-dive: caching, JSON shape, troubleshooting. Load for cost-related issues. |
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核