repo-statuslisted

Cross-machine status of ONE repo — this machine's clone and the peer's, side by side: uncommitted changes, unpushed and inbound commits, branch, age of the oldest pending work, convention versions still to adopt, open issues, and a one-line description of what each machine is mid-way through. Fetches both clones and auto-pulls the clean ones. Prints a short block per machine to the terminal, saying only what is not at its default. TRIGGER when: user asks "/repo-status", wants to know where a single repo stands, "what am I doing in this repo", "is this repo clean on the other machine", "does the desktop have unpushed work here", or "is this repo behind on conventions". DO NOT TRIGGER when: the question is about the fleet rather than one repo (use `/github-status`), or a plain `git status` on this machine answers it — this skill's reason to exist is the OTHER machine's clone and the columns git has no opinion about.
AnotherSava/claude-code-common · ★ 1 · AI & Automation · score 74

Install: claude install-skill AnotherSava/claude-code-common

## Context - Config file: !`test -f ~/.claude/skills/github-status/config/config.env && echo PRESENT || echo MISSING` - This repo: !`git rev-parse --show-toplevel 2>/dev/null || echo NOT-A-REPO` - Its origin: !`git remote get-url origin 2>/dev/null || echo NO-ORIGIN` This skill runs the same scanner `/github-status` runs, scoped to one repo with `--repo`. Everything about how a column is filled, what the cache stores, and how the peer is reached is defined there — read `~/.claude/skills/github-status/SKILL.md` when something is not covered below, rather than guessing at it. ## 1. Check the preconditions - **Config file `MISSING`** — the shared config is `/github-status`'s to create. Say so and run that skill's step 1 to write it, then come back. Do not hand-write the file. - **This repo `NOT-A-REPO` or `NO-ORIGIN`** — there is nothing to report on. Say which of the two it is and stop; do not fall back to scanning the fleet. ## 2. Run the scan ``` python ~/.claude/skills/github-status/scripts/repos-status.py --repo . ``` Use `python3` on macOS and Linux. Width resolves exactly as in `/github-status` step 2 — pass nothing here; on Windows get the console width from the **PowerShell tool** evaluating `$Host.UI.RawUI.WindowSize.Width`, subtract 2, and pass `--width <N>`. To ask about a repo you are not standing in, pass its path or its `OWNER/REPO` slug instead of `.`. A path is resolved to its slug here, so the peer finds its own clone whatever it calls the folder. T