gitviewlisted

# gitview - the state of every branch and worktree One table: worktree, whether it has uncommitted changes, branch, open pull request, ahead, behind, unpushed, and whether the branch is finished. ## Run it ```bash python3 "${CLAUDE_SKILL_DIR}/scripts/gitview.py" [PATH] ``` `PATH` defaults to the current directory. It can be a bare repository. Add `--no-pr` to skip the pull request lookup, which makes it work offline. Print the table as it comes. Do not re-sort it, re-format it, or drop rows to make it shorter. **It never fetches.** Unpushed and `gone` are only as fresh as the remote-tracking refs, and a note under the table says when this clone last fetched. If that is not recent, or no fetch is recorded, offer `git fetch --prune` and survey again before anyone relies on Unpushed or deletes anything. ## How to read it **Safe to delete is the column that answers the question.** `YES` means the branch adds nothing to the trunk, and what follows it names the proof: - `YES, adds nothing to trunk`: merging the trunk into the branch gives the trunk's tree. Computed with `git merge-tree`, which touches no checkout. - `YES, landed as abc1234`: that trunk commit carries exactly the branch's whole diff. This is a squash merge the trunk has since edited, where the tree check conflicts. - `YES, merged in PR 12`: a merged pull request's head is this exact commit. Matched on the SHA, never on the branch name. A `no` says why not: - `no, 1 file changed, 2 insertions(+)`: what the