skf-update-skill

To preserve manual content during skill updates, you can surgically regenerate only the changed exports while keeping all [MANUAL] sections intact across the process. This targeted re-extraction ensures your custom developer content remains untouched.

Provenance traceability maintains a traceable link from regenerated exports back to their upstream source. It ensures changes are fully traceable to file:line citations, providing clear evidence of what source modifications triggered the export updates.

You can detect API drift without overwriting manual sections by using gap-driven drift workflows and detect-only safety modes. These controlled update strategies identify altered exports and gaps while ensuring all [MANUAL] developer content is preserved.

Yes, you can run a dry-run update to safely check changed exports before committing. This safety mode allows you to verify targeted re-extraction results and provenance integrity without permanently altering your existing skill files.

The best way to update changed exports while maintaining source traceability is targeted re-extraction. This approach surgically refreshes only altered exports with full provenance, maintaining traceable links back to upstream source modifications.