stabilize

Run multi-platform stabilization checks for Daintree across macOS, Linux, and Windows.

49|6|Updated Nov 28, 2025
One-click install
npx skills add https://github.com/daintreehq/daintree --skill stabilize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stabilize
Source: https://github.com/daintreehq/daintree/tree/main/.agents/skills/stabilize
Command: npx skills add https://github.com/daintreehq/daintree --skill stabilize

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates a meticulous, multi-hour stabilization process for Daintree, ensuring every check is run across all platforms to guarantee a stable state for releases.

Core Features & Use Cases

  • Multi-Platform Stabilization: Sequentially runs checks on macOS, Linux, and Windows to ensure the system is stable.
  • Comprehensive Checks: Runs typecheck/lint/format, unit, integration, knip, build, smoke, and full Playwright E2E testing.
  • Intelligent Error Handling: Differentiates between flakes and real regressions, re-runs intelligently, and fixes real failures.
  • Use Case: Schedule this Skill before a release to validate the Daintree system in an overnight process.

Quick Start

Run /stabilize or $stabilize to initiate the stabilize process.

Frequently Asked Questions about stabilize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an overnight stabilization process for CI releases across multiple operating systems?

You can orchestrate a multi-hour stabilization process by running the stabilize command before a release. This validates the system sequentially across macOS, Linux, and Windows, executing comprehensive checks and full Playwright E2E testing.

How does automated E2E testing handle flakes versus real regressions during a release dry-run?

Intelligent error handling during E2E testing differentiates between flakes and real regressions. It performs intelligent re-runs for flakes and addresses real failures directly, ensuring accurate stabilization results for the release dry-run.

Do I need access to GitHub actions and scripts to run a multi-platform stabilization check?

Yes, running multi-platform stabilization checks requires access to Daintree's GitHub actions and scripts. This access allows the process to sequentially execute checks and release dry-runs across macOS, Linux, and Windows.

What is the best way to automate release dry-runs and comprehensive checks before a software release?

The best way is to schedule a deliberate, multi-hour stabilization process that handles both E2E tests and release dry-runs. This approach sequentially executes all comprehensive checks across multiple operating systems to ensure stability.

What specific checks should I run for CI stabilization before a release?

CI stabilization requires running typecheck, lint, format, unit, integration, knip, build, smoke, and full Playwright E2E testing. These checks are executed sequentially across macOS, Linux, and Windows to validate the system.