Skills changelog-automation
📦
changelog-automation
Content revision r1 Safe ⚙️ External commands🌐 Network access🔑 Env variables
Automate Changelogs and Release Notes
Manual changelog updates are easy to miss and hard to standardize. This skill helps teams build repeatable release notes from commits, PRs, and versions.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "changelog-automation" from https://skillstore.io/skills/wshobson-changelog-automation.md and its manifest at https://skillstore.io/api/skills/wshobson-changelog-automation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "changelog-automation". We need a changelog format for a library that ships monthly releases.
Expected outcome:
- A recommended changelog with Unreleased, Added, Changed, Fixed, and Security sections.
- A release entry format that includes dates, versions, issue references, and compare links.
- Guidance for keeping breaking changes visible before each release.
Using "changelog-automation". Our team wants release notes from Conventional Commits.
Expected outcome:
- A mapping from feature, fix, performance, revert, and refactor commits into release note sections.
- A recommendation to hide routine docs, style, test, build, and chore commits unless they affect users.
- A validation plan using commit message rules before merge.
Using "changelog-automation". Review our automated publishing workflow before we enable it.
Expected outcome:
- A checklist for branch protection, manual approval, token scope, and dry-run testing.
- A warning to confirm package registry permissions before automatic publishing.
- A recommendation to review generated release notes before public release.
Security Audit
Safev9 • 7/7/2026 Open versioned report
Static findings are Markdown examples, reference links, and CI secret placeholders, not hidden executable code. I found no prompt injection, credential exfiltration, or malicious network behavior in SKILL.md.
1
Files scanned
553
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
⚙️ External commands (42)
SKILL.md:23-59 SKILL.md:59-63 SKILL.md:63-69 SKILL.md:69-73 SKILL.md:73-74 SKILL.md:74-75 SKILL.md:75-76 SKILL.md:76-77 SKILL.md:77-78 SKILL.md:78-79 SKILL.md:79-80 SKILL.md:80-81 SKILL.md:81-82 SKILL.md:82-83 SKILL.md:83-87 SKILL.md:87-93 SKILL.md:93-99 SKILL.md:99-138 SKILL.md:138-142 SKILL.md:142-170 SKILL.md:170-172 SKILL.md:172-183 SKILL.md:183-187 SKILL.md:187-225 SKILL.md:225-229 SKILL.md:229-311 SKILL.md:311-315 SKILL.md:315-378 SKILL.md:378-380 SKILL.md:380-389 SKILL.md:389-393 SKILL.md:393-413 SKILL.md:413-415 SKILL.md:415-427 SKILL.md:427-433 SKILL.md:433-462 SKILL.md:462-466 SKILL.md:466-497 SKILL.md:497-501 SKILL.md:501-513 SKILL.md:513 SKILL.md:528-543
🌐 Network access (13)
🔑 Env variables (2)
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/wshobson-changelog-automation/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/wshobson-changelog-automation?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/wshobson-changelog-automation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/wshobson-changelog-automation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/wshobson-changelog-automation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
wshobson. (2026). changelog-automation security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/wshobson-changelog-automation/audits/9BibTeX citation
@techreport{wshobson-wshobson-changelog-automation-2026,
author = {wshobson},
title = {changelog-automation security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/wshobson-changelog-automation/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "changelog-automation security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "wshobson"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/wshobson-changelog-automation/audits/9"
identifiers:
- type: other
value: "skillstore:wshobson-changelog-automation:audit:9"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
Highest Skillstore Score
Author / source Skillstore Score Evidence Confidence Skillstore usage Updated
sickn33 Recommended
sickn33-changelog-automation
Skillstore Score 78
Evidence Confidence High
Skillstore usage 13
Updated
2026-08-21
wshobson Current
wshobson-changelog-automation
Skillstore Score 77
Evidence Confidence High
Skillstore usage 16
Updated
2026-08-21
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
70
Community
78
Spec Compliance
What You Can Build
Set Up Release Automation
Create a repeatable workflow for changelog generation, version bumps, tags, and release notes.
Adopt Commit Standards
Define Conventional Commit rules and map commit types to changelog sections.
Prepare Release Notes
Turn completed features, fixes, and dependency updates into clear release summaries.
Try These Prompts
Create a Basic Changelog
Use changelog-automation to draft a Keep a Changelog outline for this project. Include Unreleased, Added, Changed, Fixed, and Security sections.
Map Commit Types
Use changelog-automation to define Conventional Commit types for our team. Explain which types should appear in release notes.
Design a Release Workflow
Use changelog-automation to recommend a release workflow for a Node.js package. Include commit validation, changelog generation, and manual approval points.
Audit an Existing Process
Use changelog-automation to review our current release process. Identify gaps in commit standards, changelog quality, token permissions, and release review controls.
Best Practices
- Use Conventional Commits consistently before relying on automated changelog generation.
- Review generated release notes before publishing packages or creating public releases.
- Keep release credentials scoped to the minimum permissions required.
Avoid
- Mixing unrelated changes in one commit or pull request.
- Publishing releases automatically from unprotected branches.
- Editing generated changelog entries without updating the release workflow.
Frequently Asked Questions
Does this skill generate a changelog automatically?
It provides patterns and templates for automation. The user must run or configure the selected release tool.
Which changelog format does it follow?
It centers on Keep a Changelog and maps Conventional Commit types to readable sections.
Can it support GitHub Releases?
Yes. It includes GitHub Actions and release note template patterns that can be adapted.
Can it support Python projects?
Yes. It includes commitizen patterns for version bumps and changelog updates in Python projects.
Does it decide semantic versions?
It explains how breaking changes, features, and fixes map to major, minor, and patch releases.
What should teams review before using automation?
Teams should review branch protection, token scope, registry access, and generated release notes.