sync-log

Log Git push and pull operations to monthly Markdown files.

10|4|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/Lirsakura/skills-hub --skill sync-log
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-log
Source: https://github.com/Lirsakura/skills-hub/tree/main/skills/git-sync/sync-log
Command: npx skills add https://github.com/Lirsakura/skills-hub --skill sync-log

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a reliable way to track every push and pull operation performed on a Git repository, ensuring that you have a local, immutable record for auditing and debugging purposes.

Core Features & Use Cases

  • Local Logging: Records sync operations in a dedicated, non-Git-tracked directory.
  • Detailed Entries: Captures commit hashes, branch names, file changes, and operation status (success/failure).
  • Use Case: After a complex merge or a series of pushes, you can consult the sync logs to understand exactly when changes were made, what was affected, and if any operations failed, helping to pinpoint issues.

Quick Start

Ensure the sync-logs directory is ignored by Git and then use the write tool to append a new log entry for the current Git operation.

Frequently Asked Questions about sync-log

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

FAQPage Schema
How do I log Git push and pull operations for auditing?

To track Git sync operations for auditing, this Skill appends details like repository path, branch, commit hashes, changed files, and operation status to a local Markdown file organized by month.

Can I keep Git sync logs local without committing them to the repository?

Yes, you can keep Git sync logs local by storing them in a dedicated directory that is automatically added to .gitignore during initialization, ensuring logs are not committed to the repository.

What details are captured when tracking version control sync operations?

When tracking version control sync operations, the captured details include the repository path, branch names, commit hashes, changed files, and the operation status indicating success or failure.

How do I start tracking Git sync operations locally?

To start tracking Git sync operations locally, ensure the sync-logs directory is ignored by Git, then use the write tool to append a new log entry for the current operation to the monthly Markdown file.

Why do I need a local immutable record of Git sync operations?

You need a local immutable record of Git sync operations to audit and debug complex merges or series of pushes, helping pinpoint exactly when changes were made, what was affected, and if operations failed.