recreate-repolisted
Install: claude install-skill wardawgmalvicious/claude-plugins
# Recreating a repository after a pushed leak
A name or a credential has reached GitHub: in a file, a commit message,
a pull request, a branch name. **A rewrite in place is not the remedy.**
`refs/pull/N/head` pin every commit a pull request touched, and GitHub
serves unreachable objects by SHA until a collection on no schedule you
control. GitHub's own page says the same of clones, forks and "cached
views", and of the pull requests themselves
([references/pushed-leaks.md](references/pushed-leaks.md)). Deleting the
repository and creating it again is the immediate remedy, and the one in
the owner's hands: the pull request refs go with the repository. The
settings go with it too, which is why this is an order and not one
command: nothing else records their old values.
Two things the recreate does not undo, and step 1 names both: a
credential's exposure, and the copies in forks and clones.
Past `references/`, docs.github.com by its search,
`curl -s 'https://docs.github.com/api/search/v1?query=<q>&language=en&client_name=x'`
(no `client_name`: 400), then a hit's body,
`curl -s 'https://docs.github.com/api/article/body?pathname=<hit url>'`.
A live page that contradicts a line here wins: say so, act on the page,
and route the fix by `capture-learning`, bar a dated measured line that
names the page it overrules and the call that measured it, which a page
changed since its date sends back to re-measure. An observed claim is cited
or marked pending a doc check, and stands, marked