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
- zedarvates/frugal-skillstheir own version, first seen Nov 8, 2026
- Instafill/statuslinetheir own version, first seen Nov 1, 2026
- skrrt-sh/skillstheir own version, first seen Nov 1, 2026
- bananasfromwork/claude-code-plugintheir own version, first seen Oct 20, 2026
- rakaarwaky/agents-arwakytheir own version, first seen Oct 15, 2026
- ArangoGutierrez/claude-toolkittheir own version, first seen Oct 15, 2026
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.
PandelisZSkillupdate-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
32103210Skillmigrate-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
32103210Skillupdate-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
0mlkrizzz655335vSkillreview-bugbot
缺陷导向代码审查。用 Bugbot 子代理找 bug。
Also in 4 projects that use this
0mlkrizzz655335vSkillorigin
origin CLI 管理。安装、登录、更新、修复 origin.cursor.com 的 CLI。"disabled-environments:
Also in 3 projects that use this
Tsumugii24Skillsplit-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
Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 21
- Alexander-Tyagunov/magician★ 14same name
- ArangoGutierrez/claude-toolkit★ 4same name
- LarryStanley/pi-delegate★ 4same name
- skrrt-sh/skills★ 3same name
- 0mlkrizzz655335v/claude-skills-zh★ 2same name
- Eliasjunit/vibestretch★ 2same name
- zedarvates/botte-secrete★ 2same name
- bananasfromwork/claude-code-plugin★ 1same name
- Galliard7/skills★ 1same name
- Goodnessmbakara/codex-skills★ 1same name
11 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- build-unplannedSkill
- check-specs-alignmentSkill
- create-tasksSkill
- debugSkill
- design-architectureSkill
- design-it-twiceSkill
- design-productSkill
- domain-modelingSkill
- doubt-driven-developmentSkill
- finalize-taskSkill
- groundwork-checkSkill
- groundwork-helpSkill
- handoffSkill
- implement-taskSkill
- instrument-observabilitySkill
- just-do-itSkill
- just-do-it-swarmingSkill
- plan-taskSkill
- review-prSkill
- select-projectSkill
- setup-repoSkill
- shipSkill
- skillsSkill
- source-architecture-from-codeSkill
- source-product-specs-from-codeSkill
- source-ux-design-from-codeSkill
- split-architectureSkill
- split-specsSkill
- staged-rolloutSkill
- swarm-debugSkill
- swarm-design-architectureSkill
- task-validation-loopSkill
- test-driven-developmentSkill
- understanding-feature-requestsSkill
- use-git-worktreeSkill
- using-groundworkSkill
- ux-designSkill
- validateSkill
- vertical-sliceSkill
- work-on-next-taskSkill
- work-onSkill
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
- Very specific: line 12
Use the supplied action, install or uninstall.
- Very specific: line 18
Before modifying any file, verify the renderer's hard dependencies.
- Very specific: line 28
Read $HOME/.claude/settings.json, treating a missing file as {}.
- Very specific: line 29
If it already invokes $HOME/.claude/groundwork-statusline.sh, Groundwork owns it.
- Very specific: line 30
If a different statusLine exists, ask the user before replacing it.
- Very specific: line 32
Write this executable wrapper, substituting the resolved absolute <VERSIONS_DIR> and <PLUGIN_ROOT>:
- Very specific: line 50
Add or replace only statusLine in $HOME/.claude/settings.json, preserving all unrelated settings.
- Very specific: line 64
Read $HOME/.claude/settings.json.
- Very specific: line 66
If another command is configured, leave both it and the wrapper untouched and report that Groundwork does not own the active statusline.
“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.
Files
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.
- Before modifying any file, verify the renderer's hard dependencies. Run
command -v jqandcommand -v curl. If either command is missing, stop and report which dependency must be installed.ghis optional and only adds pull-request information. 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")"- Read
$HOME/.claude/settings.json, treating a missing file as{}. Inspect itsstatusLinevalue.- If it already invokes
$HOME/.claude/groundwork-statusline.sh, Groundwork owns it; continue so the wrapper is refreshed. - If a different
statusLineexists, ask the user before replacing it. Stop without modifying settings or the wrapper when they decline.
- If it already invokes
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" fiThen run
chmod +x "$HOME/.claude/groundwork-statusline.sh".Add or replace only
statusLinein$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 }- Report that installation is complete and Claude Code must be restarted to display it.
Uninstall
- Read
$HOME/.claude/settings.json. If nostatusLineexists, report that nothing is configured and stop. - Groundwork owns the setting only when its command invokes
$HOME/.claude/groundwork-statusline.sh. - If another command is configured, leave both it and the wrapper untouched and report that Groundwork does not own the active statusline.
- For an owned setting, remove only the
statusLinekey while preserving all unrelated settings. Then remove the wrapper. In other words, remove the wrapper only when Groundwork owns the configured statusLine. - Report that removal is complete and Claude Code must be restarted to apply it.
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
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.

