just-ship-status

Display local Git repository status with branches, PRs, tickets, and worktrees.

24|5|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/yves-s/just-ship --skill just-ship-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: just-ship-status
Source: https://github.com/yves-s/just-ship/tree/main/skills/just-ship-status
Command: npx skills add https://github.com/yves-s/just-ship --skill just-ship-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the hassle of manually tracking local repository state, identifying stale branches, orphaned worktrees, and mismatched PRs or board tickets, preventing clutter and confusion in development workflows.

Core Features & Use Cases

  • Repo Overview: Collects and displays local branches, PR statuses, board ticket progress, and active worktrees in a clear table.
  • Cleanup Recommendations: Analyzes data to suggest removing gone branches, outdated ones behind main, or unused worktrees.
  • Safe Cleanup: Only performs deletions or removals after explicit user confirmation, never touching active PRs or in-progress items.
  • Use Case: As a developer juggling multiple features, use this to quickly scan your repo after a sprint, spot a stale fix branch with no PR, and approve its cleanup to keep your workspace tidy.

Quick Start

Invoke the /just-ship-status command to get an overview of your local branches, PRs, board tickets, and worktrees along with any cleanup suggestions.

Frequently Asked Questions about just-ship-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check local Git repository status for stale branches and orphaned worktrees?

To check local Git repository status, the tool retrieves a comprehensive overview of branches, pull requests, board tickets, and worktrees. This identifies stale branches and orphaned worktrees while suggesting safe cleanup actions to prevent workspace clutter.

What is the best way to clean up gone branches and outdated worktrees after a sprint?

The best way to clean up gone branches and outdated worktrees is by analyzing repository data to recommend removing branches behind main or unused worktrees. Safe cleanup only executes deletions after explicit confirmation, never touching active PRs or in-progress items.

How do I monitor Git branch and pull request progress without manual checks?

To monitor Git branch and pull request progress without manual checks, the system requires Git commands and GitHub CLI to retrieve statuses. Optional board API integration further automates ticket progress tracking within your software engineering workflows.

Do I need GitHub CLI to monitor local repository branches and pull requests?

Yes, you need GitHub CLI to retrieve pull request statuses alongside local Git commands. While optional board API integration enhances ticket progress monitoring, the core repository status and branch tracking functionality relies on these CLI tools.

Can I safely delete stale Git branches without affecting active pull requests?

Yes, you can safely delete stale Git branches because the safe cleanup mechanism only performs removals after explicit user confirmation. It actively protects active pull requests and in-progress items from being touched during the branch cleanup process.