AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Changelog

skill-viknesh20-20-claude-code-tool-kit-changelog · by viknesh20-20

Generates a changelog from git history following Keep a Changelog format. Categorizes commits into Added, Changed, Fixed, Removed, Security, and Breaking Changes. Use before releases or to document recent work.

↗ Website ↗ Repository
— No reviews yet
0 installs
40 views
0.0% view→install

Install

$ agentstack add skill-viknesh20-20-claude-code-tool-kit-changelog

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-viknesh20-20-claude-code-tool-kit-changelog)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
○ 4mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Changelog? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Generate Changelog

Git History

!git log --oneline --no-merges -50 2>/dev/null

Tags

!git tag --sort=-v:refname 2>/dev/null | head -10

Latest Tag

!git describe --tags --abbrev=0 2>/dev/null || echo "No tags found"

Instructions

Step 1: Determine Range

  • If a tag/ref is provided, use: git log ..HEAD
  • If "last-release" is specified, find the most recent tag
  • If "unreleased" or no argument, show all commits since last tag

Step 2: Gather Commits

Run: git log --oneline --no-merges

For each commit, extract:

  • Commit hash (short)
  • Commit message
  • Author
  • Date
  • PR number (if referenced)

Step 3: Categorize

Group commits using Keep a Changelog categories:

  • Added: New features, endpoints, commands, pages
  • Changed: Modifications to existing functionality, API changes
  • Fixed: Bug fixes, error corrections
  • Deprecated: Features marked for removal
  • Removed: Deleted features, removed dependencies
  • Security: Vulnerability fixes, security improvements
  • Breaking Changes: Changes that require consumer updates

Detection heuristics:

  • feat: / feature: / add: → Added
  • fix: / bugfix: / hotfix: → Fixed
  • refactor: / update: / change: → Changed
  • remove: / delete: / drop: → Removed
  • security: / vuln: / cve: → Security
  • BREAKING: / BREAKING CHANGE: → Breaking Changes
  • Other: categorize by reading the commit message

Step 4: Format Output

# Changelog

## [Unreleased] — YYYY-MM-DD

### Added
- Description of new feature (#PR)

### Changed
- Description of change (#PR)

### Fixed
- Description of fix (#PR)

### Removed
- Description of removal (#PR)

### Security
- Description of security fix (#PR)

### Breaking Changes
- Description of breaking change (#PR)

Step 5: Save or Display

  • If a CHANGELOG.md exists, prepend the new section
  • If not, create a new CHANGELOG.md
  • Always show the generated content for review before saving

Rules

  • Follow Keep a Changelog format exactly
  • Include PR/issue references where available
  • Don't include merge commits
  • Don't include chore/ci-only commits unless significant
  • Group related commits into single entries where appropriate

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Cloud & Infrastructure