update

Update teatree core and overlays with non-destructive database migrations.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/souliane/teatree --skill update-souliane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update
Source: https://github.com/souliane/teatree/tree/main/skills/update
Command: npx skills add https://github.com/souliane/teatree --skill update-souliane

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, python3.13+, uv, and includes scripts (resource) components.

What problem does it solve?

This Skill resolves the challenge of manually updating teatree core and registered overlays to their default branch, ensuring a smooth process with safety guarantees.

Core Features & Use Cases

  • Safely Update Core & Overlays: Perform deterministic CLI commands to update teatree core and registered overlays.
  • Avoid Breaking Changes: Ensures that updates do not disrupt the running t3 codebase.
  • Self-DB Migrations: Handles in-process migrations of the teatree self-DB without data loss.

Quick Start

Run the t3 update command to update teatree and registered overlays to their default branch.

Frequently Asked Questions about update

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

FAQPage Schema
How do I safely update teatree core and overlays to the default branch?

To safely update teatree core and overlays, run the `t3 update` command, which performs deterministic updates with forward-fast-forwarding only from clean clones to ensure compatibility.

How does teatree handle database migrations during a core update?

Teatree handles database migrations in-process during updates, performing non-destructive self-DB migrations to prevent data loss while maintaining compatibility with the running t3 codebase.

Do I need Python 3.13 and git to run teatree updates on macOS?

Yes, running teatree updates on macOS or Linux requires git, Python 3.13+, and uv. These dependencies are mandatory for executing the update commands and managing the environment.

What is the best way to avoid breaking changes when updating teatree?

The best way to avoid breaking changes when updating teatree is to use the `t3 update` command, which enforces forward-fast-forwarding from clean clones to prevent disruptions to the running codebase.

Why does my teatree update fail on a modified git clone?

Your teatree update fails on a modified clone because the process requires forward-fast-forwarding only from clean clones, ensuring non-destructive updates and preventing conflicts with the running t3 codebase.