unmerged-work-census

Audits git repositories to find unmerged branches, stashes, and lost work across clones.

3|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ever-just/agentskills --skill unmerged-work-census-ever-just
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unmerged-work-census
Source: https://github.com/ever-just/agentskills/tree/main/skills/unmerged-work-census
Command: npx skills add https://github.com/ever-just/agentskills --skill unmerged-work-census-ever-just

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? On repositories worked by many agents and sessions, real work silently goes missing: branches nobody opened a PR for, PR descriptions that no longer match their branches, stale local clones in long-lived containers, and history rewrites that make old branches look ahead when their content already landed. This Skill sweeps every hiding place and proves whether each find is genuinely unlanded or just a ghost of rewritten history. ## Core Features & Use Cases - PR verification against actual diffs: Compares each open PR's description against the real branch diff to catch "docs-only" PRs hiding full feature builds. - Uniqueness adjudication: Uses git cherry patch-id comparison plus content spot-verification to separate genuinely unique patches from rewritten-history duplicates. - Full local and remote sweep: Covers remote branches with no PR, stashes, dangling commits, worktrees, ahead/behind local drift, and automation branches. - Use Case: Before deleting old branches or answering "did any work get lost", run the census to produce a table of every find with its location, content summary, verified uniqueness, and recommended disposition. ## Quick Start Ask the agent to run an unmerged-work census on this repository and report every branch, stash, and commit whose content has not verifiably landed on the default branch.

Frequently Asked Questions about unmerged-work-census

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

FAQPage Schema
How do I find unmerged branches in a git repository?▼

Run git branch -r --no-merged origin/master to list candidate branches, then inspect each with git log origin/master..origin/branch. Cross-reference against open PRs, since branches with commits but no PR are the classic forgotten-work bucket.

How do I check if a branch's changes were already merged after a rebase?▼

Use git cherry origin/master origin/branch, which compares by patch-id rather than SHA, so rewritten history does not inflate results. High counts are only a lead, so spot-verify by grepping the target branch for distinctive lines from the branch's changes.

Why does a branch show as ahead of master when its work already landed?▼

Force-pushes, rebases, and squash merges create new SHAs, so old branches appear ahead even though their content landed under different commits. Patch-id comparison with git cherry plus manual content spot-checks resolves whether the branch is a ghost.

Can a git census find work that was never pushed?▼

No. Work a remote agent session never pushed exists only inside its own container and is invisible to any other clone. The census reports everything visible from the remote and explicitly names unreachable places like other sessions' containers and teammates' laptops.

Is it safe to delete branches found during an unmerged work audit?▼

A census is strictly read-only and never deletes anything. Only delete a branch after its uniqueness has been spot-verified against the target branch, and treat disposition as a separate owner-approved step.