skills/dev-purge-gh-cache/SKILL.md
Purge GitHub Actions caches across every non-archived repo for one or more GitHub owners (users or orgs). Use when (1) the user says "purge gh cache", "clear actions cache", "delete CI cache", or invokes /dev-purge-gh-cache, (2) the user wants to free up GitHub Actions cache storage for an account/org, (3) the user names one or more GitHub owners (e.g. "Takazudo", "zudolab") and asks to wipe their Actions caches. Handles fan-out across all repos, parallel survey, bulk delete, and real-time verification.
npx skillsauth add takazudo/claude-resources dev-purge-gh-cacheInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Wipe GitHub Actions caches across all of an owner's repos in one shot. GH Actions
caches are per-repo, so "purge for an account" means iterating every repo under
that owner. scripts/purge-gh-cache.sh does the whole survey → delete → verify
fan-out; this skill just drives it.
Run the bundled script with the owner name(s) the user gave. Pass the absolute path so the script can re-invoke itself for parallel workers:
bash $HOME/.claude/skills/dev-purge-gh-cache/scripts/purge-gh-cache.sh <owner1> [owner2 ...]
Survey first without deleting anything: add --survey-only (or -n).
Owners can be users or orgs; pass several to do them in one run.
The script reports the scope (caches found, MB) before deleting, deletes via
gh cache delete --all, then re-checks and prints ✅ ALL CLEAR or the repos
that still have caches.
If the user only named one owner, just run it for that one. If they asked to
"see what's there" rather than purge, use --survey-only.
gh authenticated with repo + workflow scopes (the script preflights auth).jq available.Verify with gh cache list, never the actions/cache/usage API. That
usage endpoint is GitHub's billing figure and is recomputed on a delay — it
keeps reporting the old size/count for up to ~24h after caches are deleted,
which falsely looks like the purge failed. The script verifies with the
real-time gh cache list instead.
No export -f for xargs parallelism. When the parent shell is zsh,
exported bash functions don't survive into xargs ... bash -c subshells
("command not found"). The script parallelizes by re-invoking itself with an
internal __count / __delete subcommand instead.
gh cache delete --all exits non-zero with "No caches to delete" on an
empty repo — that's expected and the script ignores it.
After a successful purge, the GitHub Storage usage figure in the UI/billing
may still show the old size for up to ~24h; the caches themselves are gone (confirmed by the live verification step).
tools
Acceptance gate for a branch produced by an OpenAI Codex CLI run — usually Codex implementing a /big-plan epic that was handed off to it. Codex reports the work 'done' (or the user flags it WIP with corrections); this skill confirms the branch actually fulfils the original spec, fixes what falls short, and routes larger discoveries into GitHub issues. Use when: (1) User says '/finalize-codex-work', 'finalize codex work', 'confirm the codex work', 'check the codex branch', or 'codex said it's done', (2) A branch is the result of a Codex CLI session and needs verification against its spec issue/PR, (3) After assigning a /big-plan epic to Codex CLI. Pass -m/--merge to run /pr-complete -c at the end.
tools
Read a Figma design node directly from a share URL via the Figma REST API — no Dev Mode subscription, no MCP, no desktop app. Renders the node to PNG and dumps its full style/layout JSON so the design can be described, compared, or implemented. Use whenever the user gives a Figma design URL (figma.com/design/... or /file/...) and wants to see, read, inspect, reference, or implement that node — including `/fig-url-refer <url>`. This is the URL-based counterpart to `/figrefer` (which needs a Dev-plan desktop MCP); prefer this one when the input is a URL rather than a live desktop selection.
tools
Sync the user's Claude Code workflow skills into the OpenAI Codex CLI settings repo ($HOME/.codex) as Codex-native ports, fix the Codex .gitignore for new local state, then commit and push. Use when: (1) user says '/dev-codex-sync-settings-from-claude', 'sync codex settings', 'sync claude skills to codex', 'port skills to codex', or 'update codex from claude'; (2) after updating ~/.claude workflow skills (big-plan, x, x-as-pr, x-wt-teams) and Codex should catch up; (3) the $HOME/.codex repo has drifted behind $HOME/.claude. The ports are condensed Codex-native REWRITES, never file copies.
development
Analyze a video file (mov, mp4, webm, etc.) or a YouTube video by extracting still frames with ffmpeg and reading them chronologically with vision — Claude cannot ingest video files directly. Use whenever the user provides a video file path or YouTube URL and wants to know what happens in it: "read this video", "watch this video", "check this recording", "what happens in this .mov/.mp4", analyzing a screen recording of a UI bug, or verifying UI behavior captured in a video, even if they don't name this skill.