Skip to content
Back to skills

Shipflow Status

ASecurity

Quick cross-project git dashboard — branches, uncommitted changes, sync status, last commits

  • 666 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 2, 2026
ai-agentsgobashgit

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add majiayu000/claude-skill-registry --skill shipflow-status --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Shipflow Status?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Shipflow Status
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-shipflow-status/badge)](https://www.skillsdirectory.com/skills/majiayu000-shipflow-status)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: shipflow-status
description: Quick cross-project git dashboard — branches, uncommitted changes, sync status, last commits
disable-model-invocation: true
argument-hint: (no arguments needed)
---

## Context

- Current directory: !`pwd`
- PROJECTS.md: !`cat /home/claude/shipflow_data/PROJECTS.md 2>/dev/null | head -20`

## Flow

### Step 1: Read project registry

Read `/home/claude/shipflow_data/PROJECTS.md` to get the list of all projects with their paths. Also include ShipFlow itself (`/home/claude/ShipFlow`).

### Step 2: Gather git status for each project

For each project path, run these git commands (skip if path doesn't exist or isn't a git repo):

```bash
git -C [path] rev-parse --abbrev-ref HEAD 2>/dev/null    # Current branch
git -C [path] status --porcelain 2>/dev/null | wc -l     # Uncommitted changes count
git -C [path] rev-list --count @{upstream}..HEAD 2>/dev/null  # Commits ahead
git -C [path] rev-list --count HEAD..@{upstream} 2>/dev/null  # Commits behind
git -C [path] log -1 --format="%ar — %s" 2>/dev/null     # Last commit
git -C [path] stash list 2>/dev/null | wc -l              # Stashed changes
```

Run all projects in parallel using the **Task tool** with multiple agents, or sequentially with Bash if fast enough (<10s total).

### Step 3: Compile dashboard

```
══════════════════════════════════════════════════════════════════════
GIT STATUS DASHBOARD — [date]
══════════════════════════════════════════════════════════════════════

| Project          | Branch   | Uncommitted | Ahead | Behind | Last Commit           |
|------------------|----------|-------------|-------|--------|-----------------------|
| my-robots        | main     | 0           | 0     | 0      | 2d ago — Add SEO crew |
| tubeflow         | feat/ui  | 3           | 2     | 0      | 1h ago — Fix layout   |
| GoCharbon        | main     | 0           | 0     | 5      | 3d ago — New post     |
| ...              |          |             |       |        |                       |
| ShipFlow         | main     | 1           | 1     | 0      | 10m ago — Update tasks|

──────────────────────────────────────────────────────────────────────
```

### Step 4: Highlight issues

```
NEEDS ATTENTION
  ⚠️  tubeflow — 3 uncommitted changes on feat/ui
  ⚠️  GoCharbon — 5 commits behind remote
  ⚠️  ShipFlow — 1 uncommitted change (TASKS.md?)

QUICK ACTIONS
  → tubeflow: /shipflow-ship to commit and push
  → GoCharbon: git -C /home/claude/GoCharbon pull
```

Only show NEEDS ATTENTION if there are issues. Issues to flag:
- Uncommitted changes (>0)
- Behind remote (>0)
- Ahead of remote (>0, may need push)
- Detached HEAD
- No remote configured
- Stashed changes (>0)

---

## Important

- **READ-ONLY** — never modify any files or run git commands that change state.
- Include ShipFlow repo itself in the dashboard.
- Skip projects whose paths don't exist on disk.
- Skip SocialFlowz if it has no git repo.
- Target execution time: under 10 seconds total.
- If a project has no remote tracking branch, show "no remote" instead of ahead/behind counts.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.