fi-promotelisted

Copy [open] entries that exist only on the current branch onto the default branch before the branch is deleted — entries logged mid-branch would otherwise die with it. Run before branch cleanup; the pre-branch-delete hook blocks deletion until it has run. Despite the similar name it is unrelated to $fi-promote-deferred, which flips a single [deferred] entry back to [open] in place.
AltDoug/found-issues · ★ 1 · AI & Automation · score 74

Install: claude install-skill AltDoug/found-issues

Move `[open]` entries that exist only on the current branch over to the default branch, so they survive when this branch gets deleted. The `pre-branch-delete` hook will hard-block branch deletion until this runs successfully — that's the enforcement that prevents silent loss of tracked observations. ## What to do ### Step 1 — Identify what needs promoting ```bash found-issues promote ``` The CLI: - Confirms you're on a non-default branch - Compares this branch's `docs/found-issues.md` against the default branch's version - Lists `[open]` entries on this branch not yet on the default - Prints zero or more entries that need to be carried over ### Step 2 — If there are entries to promote The CLI does NOT auto-edit the default branch — that would violate the "no direct push to main" guarantee. You guide the user through opening a PR. For each listed entry, you have two paths: **Option A — Stay on current branch, open PR with `docs/found-issues.md` updated** If the current branch will be merged anyway via PR, just commit the existing entries on the current branch and open the PR normally. The entries land on the default branch through that PR. **Option B — Open a dedicated promotion PR** If the current branch won't be merged (it's exploratory, abandoned, etc.): 1. Note the source branch name: `git branch --show-current` 2. Switch to