pull-template

To merge template updates without losing session learnings, the skill extracts local learnings stored between sentinel markers and combines them with the updated template content. This preserves your local session learnings archive while overwriting safe files with the new template versions.

The best way to preserve CLAUDE.md during template synchronization is to use a merge workflow that detects an existing CLAUDE.md and keeps it intact. The process ensures the file will not be overwritten if it is already present in your local skill directory.

A smart merge handles skill bodies by reading the updated template and extracting local learnings contained within sentinel markers. It then produces a merged skill file that combines the new template content with your preserved local learnings archive.

Yes, you can overwrite methodology docs with template-safe versions while keeping local session learnings. The synchronization process overwrites safe files with the template updates but specifically preserves the session learnings archive stored between sentinel markers.

Yes, the template synchronization process cleans up temporary files after merging. The workflow handles overwriting safe files, merging skill bodies, preserving CLAUDE.md, and removing any temporary files created during the synchronization operation.

You need to use sentinel markers for preserving local learnings whenever you pull template updates that might overwrite your skill body. The merge workflow reads these markers to extract and protect your session learnings archive from being lost during the synchronization.