jbvc/changelog-automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
55
69%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
This skill's implementation playbook (resources/implementation-playbook.md) explicitly instructs using tools and GitHub Actions (semantic-release, git-cliff, GitHub workflows) that read commits, PRs, and GitHub release metadata—i.e., user-generated content from GitHub—which the automation ingests and uses to generate changelogs and drive release/versioning decisions.
- Audited
- Security analysis