Pre ship

Skill Syo-M/fable-frontend-skills/.claude/skills/pre-ship

Measured, opinionated Claude Code rules for frontend work (React / Next.js / Vite / Astro) — skills, path rules, review agents, sign-off hooks, installer & plugin. Every claim backed by committed eval reports.

Install

npx -y skills add Syo-M/fable-frontend-skills --skill pre-ship

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Pre-merge verification pipeline — runs typecheck, lint, affected tests, then security and a11y review passes scoped to what changed, and reports a single pass/fail table. Use before claiming any change is done, before opening a PR, and whenever the user asks to verify/finalize work. 日本語の依頼例:「出荷前チェック」「マージ前に確認して」「これで完成か確認」「PR出す前のチェック」。

SKILL.md

2.2 KB, 450 tokens by cl100k_base, as published. Nobody here has run it

Pre-ship pipeline

Run the gates below in order against the current change set (git diff + untracked files). Report every result verbatim — a failing gate is reported, never worked around, and the change is not "done" until all gates pass or the human explicitly accepts a documented exception.

Gates

Scope — git status + git diff --stat: list changed files; classify what they touch (boundary code? UI? styles? tests? sensitive paths?). This decides which later gates apply.
Typecheck — typecheck script (tsc --noEmit).
Lint — lint script (ESLint + Stylelint).
Affected tests — tests colocated with changed files plus anything importing them; the full suite when shared config, tokens, or shared utilities changed. Storybook play-function tests run via the Vitest addon; touched E2E specs via test:e2e.
Security pass (only if gate 1 found boundary code) — delegate to the security-reviewer agent; its verdict gates the pipeline.
A11y pass (only if gate 1 found UI changes) — delegate to the a11y-auditor agent; blocking findings gate the pipeline.
Local scanners, if installed — gitleaks protect --staged and semgrep --config .semgrep/ when the tools exist; when they don't, mark the gate SKIPPED (tool not installed) in the report. These duplicate CI gates early, they don't replace them.
Sensitive paths — if gate 1 touched CI workflows, auth/payment, headers/CSP config, lockfile-only changes, or .claude/**: stop and get explicit human sign-off before proceeding.

Report format

One table: gate → command run → result (verbatim exit/summary line) → PASS/FAIL/SKIPPED(why). Then the verdict: READY TO SHIP or NOT READY with the blocking items listed first. Never summarize a failure as "minor".

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.