file-change-tracker

Records GitLab CI/CD variables and exposes them as a JSON API for easy retrieval and updates.

Updated Mar 17, 2026

Search Tags:#automation #git #rollback #snapshot #file editing #safety guard #path scoping

One-click install

npx skills add https://github.com/songxf1024/skills --skill file-change-tracker

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: file-change-tracker
Source: https://github.com/songxf1024/skills/tree/main/file-change-tracker
Command: npx skills add https://github.com/songxf1024/skills --skill file-change-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

It prevents you from losing track of what changed during a risky editing batch by creating explicit pre-change recovery snapshots and recording post-change results for only the paths you declare.

Core Features & Use Cases

Path-scoped local Git recovery: Creates recovery points only for explicit target files/directories rather than snapshotting the whole repo.
Pre/Post guarded sessions: Runs a mandatory pre before any file changes in a batch, then runs post afterward to commit only when new changes exist in the stored path set.
User-visible rollback guidance: Surfaces recent commits/sessions and provides safe, path-scoped rollback instructions (diff preview, restore-to-pre, and revert-to-post options).

This is best when you are running model/tool workflows that generate or modify code, configs, docs, or artifacts into known locations and you want “undo with confidence” without replacing normal version control.

Quick Start

Run the file-change-tracker pre step once at the start of your change batch by passing a short reason and the exact target paths you will modify, then do the edits, and finally run post to record the outcome.

Frequently Asked Questions about file-change-tracker

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

FAQPage Schema

How do I create local git recovery points for specific file paths before editing?▼

To create local git recovery points for specific file paths, run a pre-guarded session with your declared target paths, perform your edits, then run a post-session to commit only those scoped changes. This ensures rollback safety for batch file editing.

What is path-scoped file editing rollback and how does it work?▼

Path-scoped file editing rollback is a mechanism that snapshots only declared target directories before changes, allowing you to safely revert unwanted modifications without affecting the rest of your repository's history.

Does this file snapshot approach replace my normal version control workflow?▼

No, this file snapshot approach does not replace normal version control. It provides temporary pre-change recovery snapshots and rollback guidance for risky editing batches, working alongside your existing repository history.

How do I undo unintended file changes after running an automated editing batch?▼

To undo unintended file changes after an automated editing batch, use the rollback guidance from the post-session, which offers diff previews, restore-to-pre, and revert-to-post options for your scoped paths.

Do I need a git repository to track file modifications for automated workflows?▼

Yes, you need a git repository to track file modifications, as the dependency requires git to create explicit pre-change recovery snapshots and record post-change results for your declared paths.

What are the limitations of using path-scoped snapshots for code generation safety?▼

Path-scoped snapshots require explicit target path declarations and mandatory pre/post workflow sessions, meaning undeclared files outside the scope will not be tracked or protected against mixing unintended changes.