First-Tree Gardener

What it does

Gardener is an operational skill that automates maintaining a Context Tree repository in sync with one or more source code repositories. It detects drift, files structured sync proposals as issues, opens draft PRs for proposed NODE.md changes, and helps route reviewer feedback into safe edits or follow-ups.

When to use it

Use Gardener when you need continuous alignment between codebases and a central Context Tree: onboarding a repo into tree syncs, responding to merged PRs that should update the tree, scheduling periodic drift scans, or installing a push-mode workflow for per-PR sync. It's intended for agent-driven maintenance pipelines and CI integrations.

What's included

• Scripts: none included in the skill (has_scripts=false).
• References: the skill contains extensive procedural guidance and references in its SKILL.md (has_references=false for separate folder but the body is comprehensive).
• Instructions: detailed onboarding scenarios (A–G) for push vs pull modes, daemon operation, required env vars (ANTHROPIC_API_KEY, TREE_REPO_TOKEN), and step-by-step CLI commands for sync, comment, draft-node, respond, and status checks.

Compatible agents

Agents that can run CLI commands and interact with GitHub (breeze, CI runners, Copilot-style code agents, Claude Code) will get the most value from this skill.