flaker-storage-cache-on-ci
CommunityPersist flaker data across CI caches.
System Documentation
What problem does it solve?
Persist flaker's DuckDB storage across GitHub Actions runs to preserve history and enable cross-run ingestion. The default DuckDB file location is declared via flaker.toml and must persist between runs to maintain KPI and quarantine results. This Skill provides a repeatable workflow pattern that encodes the cache key shape, fetch-depth requirements, and import-step placement used by internal flaker users.
Core Features & Use Cases
- Cache flaker data between CI runs using actions/cache@v4 with a path matching flaker.toml storage path.
- Support multi-source ingestion (vitest reports, custom adapters) by restoring and updating flaker history across runs.
- Guidance for debugging history loss when using flaker apply or flaker run with --gate options.
Quick Start
Configure your GitHub Action workflow to cache the .flaker/data file (or the path defined by flaker.toml [storage] path) and ensure fetch-depth is sufficient to derive changes across runs.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: flaker-storage-cache-on-ci Download link: https://github.com/mizchi/skills/archive/main.zip#flaker-storage-cache-on-ci Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 510,000+ vetted skills library on demand.