tree-edit

Edits and merges persons, facts, and relationships in tree.gedcomx.json genealogy files.

3|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill tree-edit-pioneeraiacademy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tree-edit
Source: https://github.com/PioneerAIAcademy/cowork-genealogy/tree/main/packages/engine/plugin/skills/tree-edit
Command: npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill tree-edit-pioneeraiacademy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Genealogy research produces corrections, new facts, and confirmed duplicate persons that must be written into the family tree file without breaking referential integrity or bypassing the Genealogical Proof Standard. This Skill performs those direct modifications to tree.gedcomx.json safely, with validation on every write. ## Core Features & Use Cases - Ad-hoc corrections and additions: Add facts, persons, relationships, and sources via tree_edit, or correct and remove existing entries by id via tree_correct, with validate-before-persist semantics. - Person merging: Collapse two tree persons confirmed identical by a proof conclusion using merge_tree_persons, which folds names and facts and repoints every research.json reference automatically. - Record and duplicate checking: Query FamilySearch record matches and possible-duplicate person hints for any person with a FamilySearch ID. - Use Case: A user says "merge these two James Flynn records" after a proof conclusion confirms identity; the Skill picks the survivor, executes the merge, and runs check-warnings to catch genealogical impossibilities. ## Quick Start Ask the assistant to correct a birth date, add an occupation fact, or merge two confirmed duplicate persons in the current genealogy project.

Frequently Asked Questions about tree-edit

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

FAQPage Schema
How do I correct a wrong date in a GedcomX family tree?▼

Use the tree_correct tool with the update_fact operation, passing the personId, factId, and only the changed fields such as the corrected date. Dates must be GedcomX-parseable: a bare year, an ISO date, or a spelled date like 12 March 1908.

How do I merge two duplicate persons in a family tree?▼

Call merge_tree_persons with the survivor and collapsed person ids after a proof conclusion at probable tier or higher confirms they are the same individual. The tool folds names and facts, repoints relationships and research.json references, and removes the collapsed person.

When should I not edit the family tree directly?▼

Direct edits are only for ad-hoc corrections and confirmed merges. Sourced facts from newly found records should flow through record-extraction and person-evidence, and concluded values are set by proof-conclusion, not by direct tree edits.

Can I check FamilySearch record hints for a person without a FamilySearch ID?▼

No. person_record_matches and person_person_matches require a FamilySearch ID such as a 4:1: ARK or bare personId. Synthetic I-prefix ids are local stubs with no FamilySearch match data.

Why did my tree edit fail with ok false errors?▼

The tree_edit, tree_correct, and merge_tree_persons tools validate the whole project before persisting, so on ok false nothing is written. Surface the returned errors to the user rather than retrying the same call.