GitAssist AI-Powered Git Workflow Helper
v1.0.0Generate commit messages from diffs, write PR descriptions, create changelogs, suggest branch names. Every git workflow, automated.
⭐ 0· 300·2 current·2 all-time
byShadow Rose@theshadowrose
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (generate commit messages, PR descriptions, changelogs, branch names) matches the included code which runs git commands and synthesizes outputs. Minor mismatch: SKILL.md and README claim 'No external API calls. Uses your local or configured AI model' / 'AI-Powered', but the shipped src/git-assist.js contains deterministic heuristics and does not call any AI model or external service.
Instruction Scope
Runtime instructions and code stay within the stated scope: they read staged diffs, branch/log/diff data from the repository and produce messages. There are no instructions to read unrelated system files or to transmit data externally.
Install Mechanism
No install spec is provided (instruction-only skill plus a source file). Nothing is downloaded or written by an installer; risk from installation mechanism is low.
Credentials
The skill requests no environment variables, credentials, or config paths. The code uses child_process to call git but does not require additional secrets or external service access.
Persistence & Privilege
Skill is not always-enabled and is user-invocable. It does not modify other skills or system-wide agent settings and does not request persistent privileges.
Assessment
This skill appears to do what it says: it runs local git commands to produce commit messages, PR summaries, changelogs, and branch-name suggestions and does not contact external services or ask for credentials. Notes before installing/using: (1) The marketing claims 'AI-powered' but the code is rule-based — expect heuristic outputs rather than calls to an LLM. (2) The tool executes git in whatever working directory you run it from; run it in a safe repository and avoid staging secrets you don't want processed. (3) Review the included src/git-assist.js yourself if you have concerns; ensure the behavior matches your expectations before using it in CI or automated workflows. (4) Verify the author/contact channels if provenance matters.Like a lobster shell, security has layers — review code before you run it.
automationvk974ygeatw0qdxx4x5kbvms61182ncjscommitsvk974ygeatw0qdxx4x5kbvms61182ncjsdevelopmentvk974ygeatw0qdxx4x5kbvms61182ncjsgitvk974ygeatw0qdxx4x5kbvms61182ncjsgit-assistvk974ygeatw0qdxx4x5kbvms61182ncjslatestvk974ygeatw0qdxx4x5kbvms61182ncjsversion-controlvk974ygeatw0qdxx4x5kbvms61182ncjs
License
MIT-0
Free to use, modify, and redistribute. No attribution required.