Flaker Storage Cache on CI
Persist flaker's DuckDB storage across GitHub Actions runs and feed it from multiple sources (vitest reports, custom adapter reports, etc.). Use when wiring `@mizchi/flaker` into a new repo's CI, adding a new ingest source to an existing flaker setup, or debugging why `flaker apply` / `flaker run --gate ...` "lost its history" between runs. Encodes the cache key shape, fetch-depth requirements, `--changed` derivation, and the import-step placement that internal flaker users converged on.
Install
npx skills add mizchi/skills --skill flaker-storage-cache-on-cigit clone --depth 1 https://github.com/mizchi/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/flaker-storage-cache-on-ci ~/.claude/skills/flaker-storage-cache-on-ciPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# flaker storage cache on GitHub Actions
`flaker` keeps its data in a DuckDB file at the path declared by `flaker.toml` `[storage] path` (default `.flaker/data`). For flaky detection / KPI / quarantine to work, that file must persist between CI runs. GitHub Actions has no first-class runtime storage, so the convention is **`actions/cache@v6` with a sliding key**.
## When this skill applies
- "新しい repo に flaker を CI で動かす"
- "flaker の履歴が CI で消えてる / 毎回ゼロからになる"
- "flaker に <source> を import するワークフロー追加して"
- "VRT / playwright / custom-adapter report を flaker に流したい"
## Cache key shape
```yaml
- name: Cache flaker data
if: always()
uses: actions/cache@v6
with:
path: .flaker/data
key: flaker-data-${{ github.run_id }}
restore-keys: |
flaker-data-
```
- `key` uses `github.run_id` so each run *writes* a new cache entry on save (GH Actions saves at end of job).
- `restore-keys: flaker-data-` matches anything written previously, falling back to the most recent — so the next run sees the latest accumulated state regardless of which earlier run produced it.
- `if: always()` so a failed earlier step still triggers the save (history-on-failure is fine and often more useful than history-only-on-success).
The `path` MUST equal `flaker.toml`'s `[storage] path`. Default is `.flaker/data` (a file, not a directory — pre-creating it as a dir breaks the DuckDB open).Details
- Skill name
flaker-storage-cache-on-ci- Repository
- mizchi/skills
- Path
flaker-storage-cache-on-ci/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Flaker Storage Cache on CI skill do?
Persist flaker's DuckDB storage across GitHub Actions runs and feed it from multiple sources (vitest reports, custom adapter reports, etc.). Use when wiring `@mizchi/flaker` into a new repo's CI, adding a new ingest source to an existing flaker setup, or debugging why `flaker apply` / `flaker run --gate ...` "lost its history" between runs. Encodes the cache key shape, fetch-depth requirements, `--changed` derivation, and the import-step placement that internal flaker users converged on.
How do I install the Flaker Storage Cache on CI skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add mizchi/skills --skill flaker-storage-cache-on-ci. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Flaker Storage Cache on CI popular?
It lives in mizchi/skills, which has 423 GitHub stars and 6 forks.
Related skills
Actions CI Tuning
423mizchi/skills
Use when auditing or improving GitHub Actions workflows for a project. Covers cache setup (npm/pnpm/yarn), job parallelism, shard-based test splitting, artifact handling pitfalls, and Playwright-specific patterns. Trigger on: slow CI, cache miss, flaky shard jobs, merge-reports failures, or an explicit 'tune CI' request.
AI Index
423mizchi/skills
Method and tooling for measuring how AI-generated a piece of prose reads, in Japanese or English. Two layers — a deterministic lint for removable surface tells (scripts/slopscore.py, no API) and a judgment layer of typed probabilistic questions (Jev noul/score) for the tells that survive editing. Includes measured human/AI baselines, a gap-first calibration procedure, and labeled fixtures. Use when building or calibrating an AI-likeness score, or when a draft needs a defensible number rather than a vibe. For writing guidance use natural-writing-ja / natural-writing-en instead.
Apm Usage
423mizchi/skills
Reference for APM manifests, installation, targeted updates, deployment paths and lockfiles. Invoke when the user explicitly asks about APM or apm.yml, or an unfamiliar APM command/error needs exact CLI details. Do not automatically invoke for every project that happens to have installed skills.
Frontend Review Testing
423mizchi/skills
Use when auditing test infrastructure — vitest coverage, playwright configuration, VRT setup, coverage merging. Produces recommendations for Week 2 testing phase. Runs `scripts/audit-coverage.sh`.
Ast Grep Practice
423mizchi/skills
Operate ast-grep as a project lint tool. Covers sgconfig.yml, fix/rewrite rules, constraints, transform, testing, and CI. Use when writing rules ast-grep can express but general-purpose linters cannot.
Gleam Practice
423mizchi/skills
Use when writing or reviewing Gleam code on the Erlang target — especially Wisp + Mist HTTP services, OTP-based processes (gen_server / supervisor analogues), justfile workflows, gleeunit testing, `gleam format`, GitHub Actions CI, and performance measurement. Trigger on `gleam.toml`, `.gleam` files, or Erlang/BEAM-related symptoms even if the user does not say "Gleam" by name.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.