Menu
Sync, build, and install the custom starship fork with jj support. Use when updating starship, rebuilding the binary, syncing with upstream, or modifying the jj_status module.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Sync this Claude Code config against new release notes — find config features added since the pinned baseline that this config should adopt. Use when Claude Code has been updated, when the user asks what's new / what changed / whether to adopt new settings or hooks, after a version bump, or when checking config currency against the latest release. Reports adoptable settings/hooks/env-vars/permissions as a risk-tiered proposal, then bumps the baseline. Do NOT use for auditing existing config quality, debugging hooks, or organizing rules — that is `maintaining-claude-code`.
Monitor and watch GitHub Actions CI/CD pipeline runs in real time. Use when the user has pushed code and wants to watch the build, check CI status, see if tests passed, monitor a pipeline, or wait for a workflow run to complete. Also use after any `jj git push` or `git push` command. Reports pass/fail with failed job logs. Do NOT use for writing or editing CI workflow YAML files, optimizing CI config, or debugging CI configuration — only for monitoring active runs.
Reorganize and clean up messy commit history on a feature branch into logical, reviewable commits. Use when cleaning up commits, preparing a branch for review, separating formatting from logic changes, fixing broken intermediate states, or squashing WIP commits.
Audit and improve Claude Code hooks, rules, and settings.json. Use when adding/debugging a hook, organizing rules, auditing settings.json (permissions, env vars, stale flags), or deciding between hook vs skill vs rule vs CLAUDE.md. For SKILL.md authoring use the skill-creator plugin; for CLAUDE.md audits use the claude-md-improver plugin.
Execute a structured test plan and emit a concise results document (JSON + Markdown). Use when running test plans, executing QA workflows, verifying acceptance criteria systematically, or producing test results documentation.
Search past Claude Code sessions to recall prior solutions, commands, fixes, and decisions. Use when the user references earlier work ("how did I fix", "last time we", "pick up where we left off", "a few months ago", "what was that … I set up", "didn't I once").
| name | managing-starship-fork |
| description | Sync, build, and install the custom starship fork with jj support. Use when updating starship, rebuilding the binary, syncing with upstream, or modifying the jj_status module. |
Manage the custom starship fork at ~/Projects/starship (origin: TrevorS/starship, upstream: starship/starship). The fork adds a jj_status module for Jujutsu VCS support on branch claude/add-jujutsu-support-JuqjU.
TrevorS/starship (the fork)starship/starshipclaude/add-jujutsu-support-JuqjU~/.local/bin/starship~/.config/starship.toml (stowed from ~/.claude/dotfiles/starship/)cd ~/Projects/starship
# Sync master
git fetch upstream
git checkout master
git merge upstream/master --ff-only
git push origin master
# Rebase feature branch
git checkout claude/add-jujutsu-support-JuqjU
git rebase master
# Build and install
cargo build --release
cp target/release/starship ~/.local/bin/starship
# Push rebased branch
git push origin claude/add-jujutsu-support-JuqjU --force-with-lease
When you've made local changes and just want to rebuild:
cd ~/Projects/starship
cargo build --release
cp target/release/starship ~/.local/bin/starship
starship --version # Should show branch name in output
starship module jj_status # Test in a jj repo — should print change ID
Source files in the fork:
src/modules/jj_status.rs — module implementation (change ID, bookmarks, conflict/divergent/hidden flags)src/configs/jj_status.rs — config struct and defaultssrc/modules/vcs.rs — VCS discovery (detects .jj/ directory)docs/config/README.md — user-facing documentationConfig in starship.toml:
[jj_status]
disabled = false # Module is disabled by default
truncation_length = 12 # Change ID display length
style = "bold purple"
symbol = "jj "
conflicted = "x" # Shown when working copy has conflicts
divergent = "?" # Shown when change is divergent
hidden = "o" # Shown when change is hidden
ignore_working_copy = true # Skip auto-snapshot for faster prompts
cd ~/Projects/starship
cargo test jj # Run jj-related tests only
cargo test # Run full test suite (slow)