agentleFS
etretr/groundwork/skills/statusline/SKILL.md

statusline

Skill45 starsChanged 4 days agoMITView on GitHub

Use when installing or uninstalling Groundwork's optional statusline configuration

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use update-cli-config, migrate-to-skills and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • PandelisZSkill

    update-cli-config

    View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.

    Also in 7 projects that use this

  • 32103210Skill

    migrate-to-skills

    Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.

    Also in 7 projects that use this

  • 32103210Skill

    update-cursor-settings

    Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.

    Also in 7 projects that use this

  • 0mlkrizzz655335vSkill

    review-bugbot

    缺陷导向代码审查。用 Bugbot 子代理找 bug。

    Also in 4 projects that use this

  • 0mlkrizzz655335vSkill

    origin

    origin CLI 管理。安装、登录、更新、修复 origin.cursor.com 的 CLI。"disabled-environments:

    Also in 3 projects that use this

  • Tsumugii24Skill

    split-to-prs

    Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.

    Also in 6 projects that use this

  • +2 more from 32103210
  • +2 more from 0mlkrizzz655335v

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 0 are distinctive, and 9 are very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 9

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the supplied action, install or uninstall.

    line 12
  2. Very specific:

    Before modifying any file, verify the renderer's hard dependencies.

    line 18
  3. Very specific:

    Read $HOME/.claude/settings.json, treating a missing file as {}.

    line 28
  4. Very specific:

    If it already invokes $HOME/.claude/groundwork-statusline.sh, Groundwork owns it.

    line 29
  5. Very specific:

    If a different statusLine exists, ask the user before replacing it.

    line 30
  6. Very specific:

    Write this executable wrapper, substituting the resolved absolute <VERSIONS_DIR> and <PLUGIN_ROOT>:

    line 32
  7. Very specific:

    Add or replace only statusLine in $HOME/.claude/settings.json, preserving all unrelated settings.

    line 50
  8. Very specific:

    Read $HOME/.claude/settings.json.

    line 64
  9. Very specific:

    If another command is configured, leave both it and the wrapper untouched and report that Groundwork does not own the active statusline.

    line 66

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Groundwork Statusline

Configure Groundwork's optional statusline only after the user explicitly invokes this workflow.

Use the supplied action, install or uninstall. When no action is supplied, default to install. Reject any other action and show /groundwork:statusline [install|uninstall].

Install

The renderer asset is ${CLAUDE_PLUGIN_ROOT}/statusline-command.sh. Claude Code does not expand ${CLAUDE_PLUGIN_ROOT} inside a user statusLine command, and marketplace installs are versioned. Install a stable wrapper at $HOME/.claude/groundwork-statusline.sh so future plugin upgrades use the newest installed Groundwork plugin version.

  1. Before modifying any file, verify the renderer's hard dependencies. Run command -v jq and command -v curl. If either command is missing, stop and report which dependency must be installed. gh is optional and only adds pull-request information.
  2. Resolve the absolute home directory, the current plugin root, and the current plugin versions directory:

    HOME_DIR="$HOME"
    PLUGIN_ROOT="$CLAUDE_PLUGIN_ROOT"
    VERSIONS_DIR="$(dirname "$CLAUDE_PLUGIN_ROOT")"
  3. Read $HOME/.claude/settings.json, treating a missing file as {}. Inspect its statusLine value.
    • If it already invokes $HOME/.claude/groundwork-statusline.sh, Groundwork owns it; continue so the wrapper is refreshed.
    • If a different statusLine exists, ask the user before replacing it. Stop without modifying settings or the wrapper when they decline.
  4. Write this executable wrapper, substituting the resolved absolute <VERSIONS_DIR> and <PLUGIN_ROOT>:

    #!/usr/bin/env bash
    # Auto-generated by /groundwork:statusline.
    base="<VERSIONS_DIR>"
    fallback="<PLUGIN_ROOT>/statusline-command.sh"
    latest=$(ls -1 "$base" 2>/dev/null | grep -E '^[0-9]+\.[0-9]+\.[0-9]+$' | sort -t. -k1,1n -k2,2n -k3,3n | tail -1)
    script="$base/$latest/statusline-command.sh"
    if [ -n "$latest" ] && [ -f "$script" ]; then
      exec bash "$script"
    elif [ -f "$fallback" ]; then
      exec bash "$fallback"
    fi

    Then run chmod +x "$HOME/.claude/groundwork-statusline.sh".

  5. Add or replace only statusLine in $HOME/.claude/settings.json, preserving all unrelated settings. Substitute the resolved absolute <HOME_DIR>; do not use ~:

    "statusLine": {
      "type": "command",
      "command": "bash <HOME_DIR>/.claude/groundwork-statusline.sh",
      "height": 3
    }
  6. Report that installation is complete and Claude Code must be restarted to display it.

Uninstall

  1. Read $HOME/.claude/settings.json. If no statusLine exists, report that nothing is configured and stop.
  2. Groundwork owns the setting only when its command invokes $HOME/.claude/groundwork-statusline.sh.
  3. If another command is configured, leave both it and the wrapper untouched and report that Groundwork does not own the active statusline.
  4. For an owned setting, remove only the statusLine key while preserving all unrelated settings. Then remove the wrapper. In other words, remove the wrapper only when Groundwork owns the configured statusLine.
  5. Report that removal is complete and Claude Code must be restarted to apply it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.