V1 Changelog
Use when generating a changelog from recent merged PRs or documenting releases. Triggers on "write changelog", "release notes", "what shipped".
Install
$ agentstack add skill-v1-io-v1tamins-v1-changelog ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-v1-io-v1tamins-v1-changelog) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
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 →About
Write Changelog
Generate a changelog for recent changes by reviewing merged PRs since the last changelog. This skill generates release notes; to sync existing docs (README, AGENTS.md, guides) with what shipped, use v1-docs-freshness.
Usage
Typical invocations:
- Claude Code:
/v1-changelog - Codex: invoke
v1-changelogfrom the skills menu or use$v1-changelog
What It Does
- Finds Latest Changelog
- Checks your changelog directory (e.g.,
docs/internal/changelog/or$CHANGELOG_DIR) - Identifies most recent changelog by date in filename
- Fetches Recent PRs
- Uses GitHub API to get all PRs merged to main since last changelog
- Extracts PR titles, descriptions, and metadata
- Generates New Changelog
- Creates markdown file with date in filename
- Formats according to project conventions
Changelog Format
The changelog follows this structure:
- 1-3 Most Impactful Changes (heading 2 each)
- Title: 1-3 words describing the change
- Description: 1-2 sentences explaining the change
- Placeholder for visual (screenshot/diagram)
- Summary of Smaller Changes (if applicable)
- High-level bullets for minor updates
Focus
- User-facing changes and new features
- Breaking changes highlighted prominently
- Major bug fixes and improvements
- Skip internal refactors unless significant
Example Structure
# Changelog - 2026-01-07
## Advanced Filtering
Added support for complex filter expressions in the query interface. Users can now combine multiple conditions using AND/OR operators and apply filters across related tables.
[Placeholder for screenshot]
## Performance Boost
Optimized query execution engine reduces average query time by 60% for large datasets through intelligent caching and parallel processing.
[Placeholder for screenshot]
## Additional Updates
- Fixed authentication timeout issues in Safari
- Improved error messages for failed data source connections
- Updated UI styling for better accessibilityNotes
- Requires GitHub CLI (
gh) to be installed and authenticated - Changelog saved to your changelog directory (e.g.,
docs/internal/changelog/YYYY-MM-DD.md) - Focuses on user impact, not technical implementation details
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: v1-io
- Source: v1-io/v1tamins
- License: MIT
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.