shelf-release

Record releases in Obsidian with auto-generated changelogs and progress entries.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/yoshisada/ai-repo-template --skill shelf-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shelf-release
Source: https://github.com/yoshisada/ai-repo-template/tree/main/plugin-shelf/skills/shelf-release
Command: npx skills add https://github.com/yoshisada/ai-repo-template --skill shelf-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Record a release in Obsidian with an auto-generated changelog and a progress entry marking the release event.

Core Features & Use Cases

  • Automated release notes: Create and store a release note in Obsidian with an auto-generated changelog from git history.
  • Progress tracking: Append a monthly progress entry to document release activity.
  • Version management: Resolve project slug/base path from config or git, and enforce idempotency to avoid duplicate notes.

Quick Start

Create a new release note in Obsidian for the current project with an auto-generated changelog.

Frequently Asked Questions about shelf-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate release notes generation in Obsidian from git history?

Automated release notes in Obsidian are generated by reading git history to create a changelog and writing a release note directly into your vault. The process also appends a monthly progress entry to track release activity.

How does version resolution work for changelog generation?

Version resolution for changelog generation works by auto-detecting the version from a VERSION file, package.json, or git tags. This ensures the correct version number applies to the release note without manual input.

Can I use this to create release notes for projects stored in an Obsidian vault?

Yes, you can create release notes for projects stored in an Obsidian vault. It resolves the project slug and base path from configuration or git to write release notes and progress entries via MCP-backed writes.

What is the best way to avoid duplicate release notes when automating changelog creation?

The best way to avoid duplicate release notes is through enforced idempotency during release-note creation. This mechanism ensures running the automation multiple times for the same release will not create duplicate entries in Obsidian.

What happens if version detection fails during Obsidian release automation?

If version detection fails during Obsidian release automation, the system uses graceful fallbacks to ensure the release-note creation process completes. This prevents failure when VERSION, package.json, or git tags are unavailable.