القائمة
Install the bundled status line — copy the script to ~/.claude/statusline.sh and wire it into settings.json. Use right after installing the statusline plugin. Re-running is safe and idempotent.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Drive Google Antigravity (agy) coding sessions as background workers — launch, send prompts, wait, read output, hand off to a human. Use when delegating coding tasks to agy, running an agy worker alongside Claude, or orchestrating agy from a controller. Mirrors claude-session-driver's command vocabulary.
Use when creating a terminal or REPL demo GIF for a README, PR, or post — recording a sequence of commands so each appears typed with its output below, no startup noise. Reach for it whenever showing a command working would land better than describing it; you don't need to be asked. Covers any REPL/CLI (irb, python, node, psql, a shell) via vhs.
Browser automation. MUST invoke before calling Playwright. Use when browsing websites, checking UI, filling forms, or automating web workflows.
Use when interacting with GitHub (issues, PRs, projects, repo exploration)
Manages Cloudflare zones via API. Use when purging cache, querying DNS records, or checking zone analytics.
Use when committing or creating branches
| name | setup-statusline |
| description | Install the bundled status line — copy the script to ~/.claude/statusline.sh and wire it into settings.json. Use right after installing the statusline plugin. Re-running is safe and idempotent. |
| user_invocable | true |
Wire this plugin's status line into the user's Claude Code config. A plugin can't
register the main statusLine setting on its own, so this one-time step does it.
Run the bundled setup script:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/setup.sh"
It:
statusline.sh to ~/.claude/statusline.sh — a stable path that survives
uninstalling the plugin (a SessionStart hook keeps it in sync after this).statusLine entry to ~/.claude/settings.json, preserving every other
setting. If a different statusLine was already set, it backs up settings.json
to settings.json.bak first.Then report to the user exactly what the script printed (synced path, whether settings.json changed or was already wired, any backup), and tell them the status line shows up on their next session — or right away if they restart Claude Code.
If the script aborts because settings.json isn't valid JSON, surface that error and
do NOT try to hand-edit the file blindly — show the user the broken file first.