Install command
Provided
skillsFirst-partyReview first Safety ✓ Privacy ✓
Git-Cliff Release Changelog Capability Pack Skill
Expert release-changelog capability pack for git-cliff with conventional commits, deterministic release notes, and low-maintenance versioning.
HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:expertType:capability-packVerified:validated
Review first — review before installing
Open the source and read safety notes before installing.
Citation facts
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
- Source URLs
- https://git-cliff.org/docs/, https://github.com/JSONbored/awesome-claude/blob/main/content/skills/git-cliff-release-changelog-capability-pack.mdx
- Package URL
- /downloads/skills/git-cliff-release-changelog-capability-pack.zip
- Package SHA256
- 88297534195c8e594486b5e5c230f5c99b1053118e534e7dbf598514e79a4741
- Safety notes
- May produce commands or configuration for live infrastructure, CI, releases, or indexing; test changes in staging or dry-run mode first., Use least-privilege API tokens and review workflow, deploy, DNS, cache, and release changes before applying them to production.
- Privacy notes
- Inputs can include repository metadata, workflow logs, deployment settings, domain names, analytics exports, and service configuration., Redact tokens, account IDs, private URLs, customer data, and proprietary deployment details before sharing generated reports or prompts.
- Platform compatibility
- claude-code (native-skill), codex (native-skill), windsurf (native-skill), gemini (native-skill), cursor (adapter), cli (manual-context)
- Author
- JSONbored
- Claim status
- unclaimed
- Last verified
- 2026-04-11
Decision playbook
Ready to evaluate for your workflow
Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.
Compare context
Selected
0
Current score
96
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
CompleteConfirm ownership and provenance before trusting install instructions.
- Done
Source link availableRequired
Open the canonical repository and verify ownership.
- Done
Source provenance statusRequired
Marked as first-party.
- Done
Metadata reviewed
Registry metadata indicates a reviewed listing.
Safety and privacy checks
CompleteValidate risk disclosures before installation or API wiring.
- Done
Safety notes presentRequired
Review the listed safety guidance before running commands.
- Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
- Done
Trust level risk gateRequired
Trust level does not block evaluation.
Package and install checks
CompleteCheck package metadata and artifact integrity signals.
- Done
Install payload available
Install or copy payload is available for review.
- Done
Package verification flag
Package marked verified.
- Done
Checksum metadata
SHA-256 hash is present.
Compare-driven decision checks
Needs reviewUse compare context to validate trade-offs before adoption.
- Pending
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
- Pending
Baseline comparison available
No baseline peer selected yet.
- Pending
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Package install
Copy-ready — paste the snippet to get started.
Config snippet
Not provided
Copy snippet
Provided
Prerequisites
3 to clear
Platforms
6 listed
Difficulty
84/100
Adoption plan
Balanced adoption plan
Current risk score 0/100. Use staged verification before broader rollout.
Pre-adoption checks
Validate source and review signals before any execution.
- Done
Confirm source provenanceRequired
Source URL/provenance metadata is present.
- Done
Confirm metadata review state
Listing has review metadata.
- Done
Verify install payload
Install/config payload exists and can be inspected.
Security checks
Confirm safety, privacy, and package integrity signals.
- Done
Review safety notesRequired
Safety notes are present.
- Done
Review privacy notesRequired
Privacy notes are present.
- Done
Verify package integrity metadata
Package verification/checksum metadata is available.
Rollout
Adopt in controlled steps based on the selected plan.
- Pending
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
- Pending
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
- Pending
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Evidence readiness matrix · balanced
Required evidence gates are covered (6/6 signals complete).
Source provenance
PresentSource repository/provenance is listed.
Required in this preset
Metadata review
PresentReview metadata is present.
Required in this preset
Safety notes
PresentSafety notes are present.
Required in this preset
Privacy notes
PresentPrivacy notes are present.
Optional in this preset
Package integrity
PresentPackage integrity metadata is present.
Optional in this preset
Install payload
PresentInstall payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
Decision timeline · balanced
6/6 steps complete with no blocking gaps for this preset.
triage
Confirm source provenanceRequired
Source/provenance metadata is available.
triage
Check metadata review statusRequired
Review metadata is available.
verify
Review safety notesRequired
Safety notes are available.
verify
Review privacy notes
Privacy notes are available.
verify
Validate package integrity metadata
Package integrity metadata is available.
rollout
Verify install payload and commandsRequired
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
Prerequisite readiness
3 prerequisites to line up before setup.
General3
Safety & privacy surface
Safety & privacy surface
2 safety and 2 privacy notes across 3 risk areas. Review closely: credentials & tokens.
- SafetyExecution & processesMay produce commands or configuration for live infrastructure, CI, releases, or indexing; test changes in staging or dry-run mode first.
- SafetyCredentials & tokensUse least-privilege API tokens and review workflow, deploy, DNS, cache, and release changes before applying them to production.
- PrivacyData retentionInputs can include repository metadata, workflow logs, deployment settings, domain names, analytics exports, and service configuration.
- PrivacyCredentials & tokensRedact tokens, account IDs, private URLs, customer data, and proprietary deployment details before sharing generated reports or prompts.
Safety notes
- May produce commands or configuration for live infrastructure, CI, releases, or indexing; test changes in staging or dry-run mode first.
- Use least-privilege API tokens and review workflow, deploy, DNS, cache, and release changes before applying them to production.
Privacy notes
- Inputs can include repository metadata, workflow logs, deployment settings, domain names, analytics exports, and service configuration.
- Redact tokens, account IDs, private URLs, customer data, and proprietary deployment details before sharing generated reports or prompts.
Prerequisites
- Conventional commit policy
- Git tags access
- Release workflow ownership
Schema details
- Install type
- package
- Reading time
- 8 min
- Difficulty score
- 84
- Troubleshooting
- Yes
- Breaking changes
- No
Package metadata
- Package verified
- Yes
- SHA-256
- 88297534195c8e594486b5e5c230f5c99b1053118e534e7dbf598514e79a4741
Skill and platform metadata
- Skill type
- capability-pack
- Skill level
- expert
- Verification
- validated
- Verified at
- 2026-04-11
Retrieval sources
https://git-cliff.org/docs/https://www.conventionalcommits.org/en/v1.0.0/https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases
Tested platforms
ClaudeCodexOpenClawCursorWindsurfGemini
| Platform | Support | Install path |
|---|---|---|
| claude-code | Native | .claude/skills/<skill-name>/SKILL.md |
| codex | Native | .agents/skills/<skill-name>/SKILL.md |
| windsurf | Native | .windsurf/skills/<skill-name>/SKILL.md |
| gemini | Native | .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md |
| cursor | Adapter | .cursor/rules/<skill-name>.mdc |
| cli | Manual | AGENTS.md or tool-specific context file |
Full copyable content
# Trigger
"Apply the git-cliff release changelog capability pack for this release."
# Required output
1) Conventional commit compliance report
2) Proposed release version and rationale
3) Generated changelog sections
4) Tag/release execution checklistAbout this resource
Knowledge Freshness
This capability pack is pinned to documentation verified on 2026-04-11.
Retrieval Sources
- https://git-cliff.org/docs/
- https://www.conventionalcommits.org/en/v1.0.0/
- https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases
Core Workflow
- Validate commit history quality against conventional commit policy.
- Determine next version from merged change scope.
- Generate changelog draft and remove low-signal noise.
- Stage release commit/tag plan with rollback path.
- Publish release and verify changelog consistency.
Overview
This skill gives agents a deterministic release process that produces readable changelogs without manual rewrite churn.
Capability Scope
- Commit history normalization
- Semver recommendation logic
- Changelog generation and section tuning
- Release tagging and publication checks
- Post-release verification and correction
Compatibility
Native
- Claude Code / Claude: native skill usage via
SKILL.md. - Codex/OpenAI workflows: compatible with Agent Skills-style
SKILL.mdcontent as reusable workflow instructions.
Manual Adaptation
- Gemini CLI: native skill usage via
.gemini/skills/<skill-name>/SKILL.mdor.agents/skills/<skill-name>/SKILL.mdwhere supported. - Cursor: use the generated
.cursor/rules/*.mdcadapter for project rules. - OpenClaw and similar agents: use the same skill content as a reusable prompt/workflow file when native skill import is unavailable.
Production Rules
- Enforce conventional commits before changelog generation.
- Keep release source-of-truth tied to tags on protected branches.
- Exclude bot-only and merge-noise commits from user-facing notes.
- Require human review before publishing release artifacts.
Troubleshooting
Issue: Changelog section grouping is noisy
Fix: tighten commit scopes and skip bots/merge-only commits.
Issue: Wrong version bump recommendation
Fix: map feat/fix/breaking conventions explicitly in config.
Issue: Release notes differ from changelog
Fix: derive both from same generated artifact path.
Output Contract
- Proposed version with justification.
- Clean changelog text ready for merge.
- Tag/release command sequence.
- Verification notes and fallback steps.
Source citations
Add this badge to your README
Show that Git-Cliff Release Changelog Capability Pack Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/skills/git-cliff-release-changelog-capability-pack)How it compares
Git-Cliff Release Changelog Capability Pack Skill side by side with 2 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).
Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.
| Field | Expert release-changelog capability pack for git-cliff with conventional commits, deterministic release notes, and low-maintenance versioning. Open dossier | Expert release changelog generation capability pack for drafting, validating, and publishing user-facing release notes from conventional commits, tags, and GitHub Releases with source-backed review matrices and privacy-safe output. Open dossier | Expert husky capability pack for lightweight local quality gates, commit message enforcement, and low-friction contributor workflows. Open dossier |
|---|---|---|---|
| Next stepsDiffers | |||
| Trust | |||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trustDiffers | Package verified2026-04-11 | Package not verified | Package verified2026-04-11 |
| Source provenanceDiffers | Source-backed | Submission linkedSource submission | No submission link |
| SubmitterDiffers | — | kiannidev | — |
| Install risk | Review first | Review first | Low risk |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — |
| Category | skills | skills | skills |
| Source | first-party | source-backed | first-party |
| Author | JSONbored | kiannidev | JSONbored |
| Added | 2026-04-11 | 2026-06-15 | 2026-04-11 |
| Platforms | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI |
| Source repo | — | — | — |
| Safety notes | ✓May produce commands or configuration for live infrastructure, CI, releases, or indexing; test changes in staging or dry-run mode first. Use least-privilege API tokens and review workflow, deploy, DNS, cache, and release changes before applying them to production. | ✓This skill plans release publication; it must not create tags, publish releases, or push version bumps without explicit maintainer approval. Security and breaking-change entries can affect downstream consumers; require owner review before public release. Automated changelog tools may include contributor handles or internal ticket IDs; scrub before publishing. Do not run release scripts or CI publish workflows from unreviewed fork contexts. | ✓Installs from a downloaded package and may run local commands or scaffold files as part of the workflow; review the package and any generated changes before applying. |
| Privacy notes | ✓Inputs can include repository metadata, workflow logs, deployment settings, domain names, analytics exports, and service configuration. Redact tokens, account IDs, private URLs, customer data, and proprietary deployment details before sharing generated reports or prompts. | ✓Changelog drafts may expose unreleased features, customer names, internal URLs, and security fix details. GitHub compare views and release automation logs can include private repository metadata. Redact embargoed vulnerability details and internal-only migration notes from public release text. Keep registry tokens, npm credentials, and signing keys out of prompts and generated notes. | ✓Operates on your local project files and any context you share in the session; review what you expose before sharing — nothing is sent beyond the model unless a step calls an external service. |
| Prerequisites |
|
|
|
| Install | | — | |
| Config | — | — | — |
| Citations | |||
| Claim | Unclaimed | Unclaimed | Unclaimed |
Featured in
Signals
Loading live community signals…
More like this, weekly
A short, calm digest of reviewed Claude resources. Unsubscribe any time.