release-changelog Skill
Generate the stable Paperclip release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag. Published by microsoft in amplifier-app-paperclip.
Decision snapshot
Is this a fit?
Developers using amplifier-app-paperclip, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is release-changelog Skill?
Generate the stable Paperclip release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag. Published by microsoft in amplifier-app-paperclip. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using amplifier-app-paperclip
Declared skill metadata
- Source file: .agents/skills/release-changelog/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use release-changelog Skill
- Use it for developers using amplifier-app-paperclip.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-app-paperclip
- Skill file: .agents/skills/release-changelog/SKILL.md
What it does
Generate the stable Paperclip release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.
Skill instructions
Release Changelog Skill Generate the user-facing changelog for the stable Paperclip release. Versioning Model Paperclip uses calendar versioning (calver): - Stable releases: YYYY.MDD.P (e.g. 2026.318.0) - Canary releases: YYYY.MDD.P-canary.N (e.g. 2026.318.1-canary.0) - Git tags: vYYYY.MDD.P for stable, canary/vYYYY.MDD.P-canary.N for canary There are no major/minor/patch bumps. The stable version is derived from the intended release date (UTC) plus the next same-day stable patch slot. Output: - releases/vYYYY.MDD.P.md Important rules: - even if there are canary releases such as 2026.318.1-canary.0, the changelog file stays releases/v2026.318.1.md - do not derive versions from semver bump types - do not create canary changelog files Step 0 — Idempotency Check Before generating anything, check whether the file already exists: bash ls releases/vYYYY.MDD.P.md 2/dev/null If it exists: 1. read it first 2. present it to the reviewer 3. ask whether to keep it, regenerate it, or update specifi
Verified compatibility and discovery
Frequently asked questions
What is release-changelog?
release-changelog is a open-source AI agent skill with Copy skill directory. Generate the stable Paperclip release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.
Who is release-changelog best for?
release-changelog is best for reusing agent instructions, scripts, and references.
How do I install release-changelog?
Install or run release-changelog using Copy skill directory. Check release-changelog for the latest setup command.
Is release-changelog actively maintained?
release-changelog may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
