Git Changelog Generator
v1.0.0Generate changelogs from git commits. Supports markdown, plain text, and JSON output with date ranges and tag-based filtering.
⭐ 0· 1.1k·8 current·8 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the included script and SKILL.md. The script operates on a local git repository and produces markdown/plain/text/JSON changelogs as advertised. No unrelated binaries, env vars, or config paths are requested. (Minor note: the script shebang points to /opt/homebrew/bin/bash, but examples call it with 'bash scripts/changelog.sh', so this is not an operational mismatch.)
Instruction Scope
Runtime instructions only invoke the included shell script against a repo path. The script only runs git commands, changes to the provided repository path, and formats commit metadata. It does not reference external endpoints, other system config, or environment variables. Users should be aware that commit messages/metadata may contain sensitive information and will be output.
Install Mechanism
No install spec; skill is instruction-only with one included script. Nothing is downloaded or written to disk by an installer. Dependencies are limited to git and bash, which matches the script's behavior.
Credentials
No environment variables, credentials, or config paths are required. The script does not read shell history or other unrelated files. There is no disproportionate access requested.
Persistence & Privilege
always is false and the skill does not request persistent presence or modify other skill/system configs. It can be invoked by the agent (normal default), but it does not autonomously elevate privileges or store tokens.
Assessment
The skill appears to do what it says: run the provided script against a local git repository to generate a changelog. Before using: (1) inspect or run the script in a sandbox — although harmless-looking, it will output all commit messages and metadata (these can contain secrets); (2) note the shebang points to /opt/homebrew/bin/bash but examples invoke it with 'bash', which avoids shebang issues; (3) ensure you run it only on repositories you trust or where exposing commit text is acceptable. Overall it's coherent and does not request extra permissions or network access.Like a lobster shell, security has layers — review code before you run it.
latestvk97e42v2d9544byv08qy73x11x81bvsr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.