Stop flaky tests from blocking PRs while you fix them
Quarantine known flaky tests into a separate lane so they don't block merges, while preserving visibility and enforcing a fix-by deadline.
Create a skill called "Flaky Test Quarantine". The skill must: - Define how to identify flaky tests (reruns + fingerprints) - Propose the quarantine mechanism for our test framework - Specify CI changes: separate lane, reporting, and non-blocking behavior - Provide a tracking template (owner, SLA, exit criteria) Output in Markdown plus example snippets (pseudo-code acceptable).
Flaky tests destroy trust and waste developer time. This recipe sets up a quarantine
pattern: detect → tag → isolate → fix → unquarantine.
Separate flakes from regressions and route the fix
Turn CI failures into categorized, actionable tickets by detecting flaky behavior, extracting failure fingerprints, and recommending next actions with ownership.
Cut pipeline time with caching, parallelism, and smarter triggers
Reduce CI wall-clock time by implementing dependency caching, parallelization/sharding, and filtering out unnecessary pipeline runs.
Ship new creatives every week without chaos
Creative teams burn out when "we need new ads" arrives as an emergency. This recipe creates a weekly sprint system: inputs, brief template, production checklist, QA, and a testing plan that compounds learning.
Improve retention with scroll-stopping openings
Generates and rewrites hooks optimized for your platform and audience intent. It produces multiple hook styles (curiosity, contrast, payoff-first) and recommends which to test, based on your goals and content type.