Prompt Git

v1.0.2

Git for your prompts. Track every change, diff versions, rollback mistakes, never lose a good prompt again. All local, zero dependencies, works offline.

0· 256·1 current·1 all-time
byShadow Rose@theshadowrose
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (prompt version control) matches what the files implement: local storage under ~/.promptgit, save/get/diff/rollback, search, and export/import. No unexpected cloud or privileged capabilities are requested.
Instruction Scope
SKILL.md CLI examples and usage align with the code. Runtime instructions operate on local files and the repository; they don't instruct the agent to read unrelated system files, network endpoints, or environment variables.
Install Mechanism
There is no install spec (instruction-only skill for CLI usage). The included Python scripts rely only on the standard library and run locally. No external downloads or installers are used.
Credentials
The skill requests no environment variables, credentials, or config paths. All storage is local (default ~/.promptgit). The requested access is appropriate for a local versioning tool.
Persistence & Privilege
The skill is not forced-always or otherwise privileged. It does write files to a user-owned directory (~/.promptgit) as expected for a local CLI tool; it does not modify other skills or system-wide agent settings.
Assessment
This appears to be a straightforward local tool. Before installing or running: 1) Review any prompts you import from others — imports can overwrite or create history locally and may include secrets; don't import files from untrusted sources. 2) The repository defaults to ~/.promptgit — if you put that directory into cloud-sync (Dropbox/Drive/Git), your prompts (including potentially sensitive system prompts) will be stored in the cloud. 3) There's no concurrency locking: avoid running simultaneous operations against the same repo to prevent corruption. 4) The code is human-readable; if you need stronger guarantees (encryption, access control, cloud sync), consider additional tooling. Overall, the skill is coherent with its stated purpose.

Like a lobster shell, security has layers — review code before you run it.

gitvk97080hj6yr28q65m14sra3m4982m2d7latestvk97080hj6yr28q65m14sra3m4982m2d7managementvk97080hj6yr28q65m14sra3m4982m2d7promptsvk97080hj6yr28q65m14sra3m4982m2d7trackingvk97080hj6yr28q65m14sra3m4982m2d7version-controlvk97080hj6yr28q65m14sra3m4982m2d7

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments