skills/dev-create-b4push-script/SKILL.md
Create a before-push validation script (b4push) and project-level b4push skill. Analyzes the project, identifies check steps (quality, build, test, doc site, e2e), generates scripts/run-b4push.sh, adds package.json entry, creates .claude/skills/b4push/SKILL.md. Use when: (1) User says 'create b4push', 'add b4push', 'before push script', (2) Setting up a new project's CI/validation workflow.
npx skillsauth add takazudo/claude-resources dev-create-b4push-scriptInstall 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.
Generate a before-push validation script (scripts/run-b4push.sh), wire it into package.json, and create the project-level .claude/skills/b4push/SKILL.md.
All templates and step tables live in the /b4push-wisdom skill — the single canonical source. Read it before generating anything; do not keep a second copy of the templates here. This skill is the focused "just create the local script + skill" entry point; /b4push-wisdom is the full guide (local script + skill + CI workflow).
check, build, test, lint, format, typecheck), doc site (doc/, docs/, website/), e2e tests (playwright/cypress), data-generation scripts. See /b4push-wisdom Step 1./b4push-wisdom Step 2.scripts/run-b4push.sh — use the template in /b4push-wisdom Step 3, then chmod +x scripts/run-b4push.sh.package.json script — "b4push": "./scripts/run-b4push.sh" (/b4push-wisdom Step 4)..claude/skills/b4push/SKILL.md — use the project-skill template in /b4push-wisdom Step 5. Uppercase SKILL.md is canonical; lowercase skill.md causes git dual-tracking / clone collisions on case-insensitive filesystems. Give it user-invocable: true and allowed-tools: [Bash], with a description whose triggers fire on big changes, PR completion, etc.pnpm b4push and fix any issues found.For the optional GitHub Actions CI workflow and the reference-project list, see /b4push-wisdom.
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.