← ClaudeAtlas

stack-gotchaslisted

Use when hitting a known failure in my stack — release-please rate-limit or auto-merge loop, GitHub Pages env branch-policy, Supabase egress/RLS/stale-client-blob, a Flipper FAP release/build/version-triad failure or a FAP whose UI won't refresh when launched from favourites/quick-buttons, or verifying mobile/responsive rendering in WSL — for a direct diagnose-and-recover recipe.
Endika/eskills · ★ 0 · Code & Development · score 72
Install: claude install-skill Endika/eskills
# stack-gotchas ## Overview Diagnose-and-recover recipes for failures I've actually hit. Each is **symptom → what it really means → fix** — not a tutorial. Match the symptom, apply the recipe. ## release-please: "Resource not accessible by integration" - **Symptom:** release-please fails at "Creating N releases…" despite correct token perms. - **Means:** GitHub **secondary** rate-limit (abuse detection) on the `github-actions[bot]` token, _not_ a permissions bug. Tell-tale: a release succeeded seconds earlier; `gh api rate_limit` core looks healthy. Usually triggered by a burst (dependabot opening ~12 PRs). - **Fix:** (1) create the missing release with **your user token**, full 40-char SHA: `gh release create vX.Y.Z --target <full-sha> --title vX.Y.Z --notes "<CHANGELOG section>" --latest`. (2) Swap the PR label `autorelease: pending` → `autorelease: tagged` via REST (`gh api`), or it retries forever. (3) Let the bot cooldown clear (~minutes–1h) with no more content-creation calls. Code usually deployed anyway (Pages runs on push independently). ## release-please: infinite auto-merge loop - **Symptom:** the release PR never merges; the workflow re-dispatches itself every ~90s. - **Means:** the bot's PR (made with `GITHUB_TOKEN`) gets **no CI run** → the required `verify` check never appears → auto-merge can't complete; it lands only via a fragile fast-forward that breaks if `main` advanced by hand in parallel. - **Fix:** create the tag/release yourself at