file-change-tracker
v1.0.0Mandatory before the first file-changing action in a new edit batch. Use before creating, editing, overwriting, patching, renaming, moving, deleting, or gene...
⭐ 0· 101·0 current·0 all-time
bySong Xianfeng@songxf1024
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill is a local file-change protector that uses git and shell. Declared requirements (git and a shell) match the functionality. There are no unrelated credentials, network endpoints, or unrelated binaries requested.
Instruction Scope
SKILL.md and scripts instruct the agent (and user) to run ./scripts/helper.sh pre/post around explicit paths. The script only touches the workspace and writes state under .git/.guarded-edit, scopes operations to the provided target paths, and will initialize a local git repo and set repo-local user.name/email if none exist. Initializing a repo and writing commits/index state is within the skill's purpose but is a persistent filesystem-side effect users should be aware of.
Install Mechanism
This is instruction-only with an included helper.sh; there is no installer that downloads external code. No remote downloads or package installs are performed by the skill itself.
Credentials
The skill requests no environment variables or credentials. It only relies on local git and shell — appropriate for its operation. It does set repo-local git config keys (user.name and user.email) if absent, which is proportional but should be noted by users who care about repo metadata.
Persistence & Privilege
The skill writes persistent state into the repository's .git directory (.git/.guarded-edit) and creates commits (guard(pre)/guard(post)). It may initialize a git repo in a non-git directory. It does not request always:true and does not modify other skills or global agent settings.
Assessment
This skill appears to do exactly what it says: create local git-backed PRE/POST snapshots limited to explicit target paths. Before installing or running it, review the helper.sh and accept that it will: (1) create or modify .git in your workspace (it will init a repo if none exists), (2) create local commits and update the index for the declared paths, and (3) set repo-local git user.name/user.email if they are missing. Do not include sensitive files in the declared target paths; use guarded-edit.ignore to exclude paths. If you do not want a git repo created in the current directory, do not run this skill there. If you want extra assurance, run the script in a disposable copy of the workspace first and inspect .git/.guarded-edit and the created commits.Like a lobster shell, security has layers — review code before you run it.
latestvk9717afz093gtdxm7thecq40h183d53y
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🛟 Clawdis
Binsgit
Any binbash, sh
