gardener

Automate Context Tree maintenance via drift detection and structured verdicts.

122|33|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/agent-team-foundation/first-tree --skill gardener
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gardener
Source: https://github.com/agent-team-foundation/first-tree/tree/main/skills/gardener
Command: npx skills add https://github.com/agent-team-foundation/first-tree --skill gardener

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Gardener automates maintenance tasks for the Context Tree, handling reviewer feedback on tree-sync PRs, posting structured verdict comments on source-repo PRs/issues, and (in push-mode) installing an event-driven workflow to replace a long-running gardener service.

Core Features & Use Cases

  • Automates drift detection and triage for tree repository PRs and bound source repos.
  • Posts structured verdicts, assigns tree-node owners, and supports end-to-end on-boarding workflows.
  • Supports both push-mode workflows and pull-mode daemons for continuous monitoring of multiple repos.

Quick Start

Install the push-mode workflow in your codebase and start the gardener to begin drift detection and automated feedback.

Frequently Asked Questions about gardener

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

FAQPage Schema
How do I automate drift detection for GitHub pull requests across multiple repositories?

Automating drift detection for GitHub PRs across multiple repositories is achieved by running a daemon in pull-mode or installing an event-driven workflow in push-mode. The system continuously monitors bound source repos and their tree repos to detect and triage drift automatically.

What is automated context tree maintenance and how does it handle PR review feedback?

Automated context tree maintenance detects drift in tree-sync PRs and handles reviewer feedback through structured verdict comments on source-repo PRs. It assigns tree-node owners and automates triage, applying human oversight to CI code-repo gating and auto-issue creation.

Do I need a Claude or Anthropic API token to automate code-repo gating and issue creation?

Yes, you need Claude or Anthropic API integration to automate code-repo gating and auto-issue creation. You also need a tree-repo token for merge-to-issue operations, plus configuration defined in the .claude/gardener-config.yaml file to establish push or pull mode.

Does the gardener automation tool support both push-mode workflows and pull-mode daemons for continuous monitoring?

Yes, the automation tool supports both push-mode event-driven workflows and pull-mode long-running daemons for continuous monitoring. Push-mode installs directly into your codebase, while pull-mode uses a daemon to monitor multiple bound source repos simultaneously.

How do I configure automated verdict comments and tree-node owner assignments for CI workflows?

Configuring automated verdict comments and tree-node owner assignments requires reading settings from the .claude/gardener-config.yaml file. The system then posts structured verdicts on source-repo PRs and launches a breeze client to handle notifications for CI workflows.

What are the limitations when automating tree-sync PR triage with human oversight?

Automating tree-sync PR triage requires both a Claude API integration and a tree-repo token for merge-to-issue operations, meaning it cannot function without these dependencies. It also relies on human oversight for end-to-end onboarding workflows and proper configuration.