work-logs-sync

Synchronize work-log markdown files to the latest template.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/younwony/younwony.github.io --skill work-logs-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-logs-sync
Source: https://github.com/younwony/younwony.github.io/tree/main/.claude/skills/data/work-logs-sync
Command: npx skills add https://github.com/younwony/younwony.github.io --skill work-logs-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill synchronizes all existing work-log markdown files to a new template when the guide/template changes, preventing drift and manual rewrite.

Core Features & Use Cases

  • Automated template migration: updates all docs/career/work-logs/**/*.md to the new structure without data loss.
  • Change propagation: ensures all career work logs reflect latest guidelines.
  • Use Case: After updating the work-log template in SKILL.md, run the skill to reformat all existing work logs for consistency.

Quick Start

Run the synchronization to align docs/career/work-logs/**/*.md with the updated work-log template. The process should be executed inside your project workspace and the changes should be committed with git.

Frequently Asked Questions about work-logs-sync

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

FAQPage Schema
How do I update multiple markdown work logs to a new template at once?

Batch-updating markdown work logs involves synchronizing files matching docs/career/work-logs/**/*.md to the latest template structure in place. This process applies the new format across all existing files simultaneously without manual rewriting.

Can I synchronize markdown files to a new template without losing existing data?

Yes, synchronizing markdown work logs to a new template can be non-destructive. The process preserves existing data while applying the updated structure, ensuring no content is lost during the template migration.

Do I need external dependencies to batch-update work log markdown files?

No external dependencies are required to batch-update work log markdown files. The synchronization process relies only on standard tooling, requiring no additional packages to reformat docs/career/work-logs/**/*.md files.

What's the best way to prevent template drift in existing markdown documentation?

The best way to prevent template drift in markdown documentation is running an automated synchronization process after guide updates. This propagates the latest template changes to all existing work logs, keeping them consistent.

Are staged git changes available after synchronizing work log templates?

Yes, staged git changes are available after synchronizing work log templates. The process updates files in place and ends with all modifications staged, making them ready for an immediate git commit.