release-process
Full release workflow for obsidian-gemini: update release notes, run checks, bump version with npm, create a GitHub release, and verify. Use this skill when preparing a new plugin release.
Best use case
release-process is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Full release workflow for obsidian-gemini: update release notes, run checks, bump version with npm, create a GitHub release, and verify. Use this skill when preparing a new plugin release.
Teams using release-process should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/release-process/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How release-process Compares
| Feature / Agent | release-process | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Full release workflow for obsidian-gemini: update release notes, run checks, bump version with npm, create a GitHub release, and verify. Use this skill when preparing a new plugin release.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Release Process ## When to use this skill Use this skill when: - You need to create a new release of the plugin - The user asks to bump the version, publish, or ship a release - You need to understand the release workflow or version management ## Release steps Follow these steps in order to create a new release: ### 1. Update Release Notes (`src/release-notes.json`) - Add a new entry at the top of the JSON object for the new version - Include a title, highlights (array of bullet points), and details - Follow the emoji pattern used in existing releases - This file is the single source of truth for both the in-app modal and the docs site changelog ### 2. Run Tests and Build ```bash npm test # Ensure all tests pass npm run build # Verify production build succeeds ``` ### 3. Commit Release Notes ```bash git add src/release-notes.json git commit -m "Add release notes for version X.Y.Z" ``` ### 4. Bump Version (Choose appropriate semantic version) ```bash npm version patch # Bug fixes (4.1.0 -> 4.1.1) npm version minor # New features (4.1.0 -> 4.2.0) npm version major # Breaking changes (4.1.0 -> 5.0.0) ``` The `npm version` command automatically: - Updates `package.json` version - Runs `version-bump.mjs` to update `manifest.json` and `versions.json` - Creates a git commit with the version change - Creates a git tag (e.g., `4.1.1`) - Pushes the commit and tag to GitHub (via `postversion` script) ### 5. Update GitHub Release A GitHub Actions runner automatically creates a draft release when a tag is pushed. After the tag is pushed: - Go to https://github.com/allenhutchison/obsidian-gemini/releases - Find the auto-generated release for the new tag - Update the release notes body with content from `src/release-notes.json`, formatted as Markdown - Mark the release as **"Set as the latest release"** - Publish the release (if still in draft) ### 6. Verify Release - Check that the release appears on GitHub and is marked as "Latest" - Verify the tag matches the version - Test installation in a test vault (if needed) ## Important rules - Do NOT manually edit version numbers in `package.json`, `manifest.json`, or `versions.json`. Always use the `npm version` commands. - Always update release notes BEFORE running `npm version`. - Ensure you're on the master branch and it's up to date before releasing. ## Build system context - Uses esbuild for fast bundling with TypeScript - Custom text file loader for `.txt` and `.hbs` templates - Source maps inline in dev, tree shaking in production - Generated artifacts (`main.js`, `manifest.json`, `versions.json`) stay in the repo root for Obsidian
Related Skills
vault-semantic-search
Search vault notes by meaning using semantic search (RAG). Activate this skill when users want to find notes by concept or topic rather than exact keywords, or when keyword search tools return poor results.
recall-sessions
Search past agent conversations to recall prior discussions, decisions, and context. Activate this skill when users ask about previous conversations, want to resume past work, or reference earlier decisions.
obsidian-properties
Work with Obsidian note properties (frontmatter). Activate this skill when users want to add, modify, or organize properties, understand property types, format YAML frontmatter, or use properties with templates, search, or Bases.
obsidian-bases
Create and configure Obsidian Bases — database-like views of notes. Activate this skill when users want to create bases, write filters, formulas, or set up table/cards/list/map views.
image-generation
Generate images from text descriptions and save them to the vault. Activate this skill when users want to create illustrations, diagrams, visual content, or any AI-generated images.
gemini-scribe-help
Answer questions about Gemini Scribe plugin features, settings, and usage. Activate this skill when users ask how to use the plugin, configure settings, or troubleshoot issues.
deep-research
Conduct comprehensive, multi-source research and generate cited reports. Activate this skill when users want in-depth research on a topic, need synthesis across web and vault sources, or want a structured research report saved to their vault.
audio-transcription
Transcribe audio and video files into structured notes. Activate this skill when users want to transcribe recordings, meetings, podcasts, voice memos, or any audio/video content in their vault.
ui-ux-guidelines
UI/UX best practices for obsidian-gemini plugin development. Covers modal sizing, text overflow, message formatting, collapsible UI, animations, icons, file chips, session state, CSS containment, and theme compatibility. Use this skill when building or modifying UI components.
obsidian-plugin-development
Build, modify, and debug Obsidian plugins using the TypeScript API. Use this skill when working with Obsidian plugin source code, the obsidian npm package, plugin UI (views, modals, settings, commands, ribbons), vault file operations, editor manipulation, workspace management, metadata cache, events, markdown rendering, or the Obsidian CLI. Covers plugin lifecycle, best practices, common patterns, and the full TypeScript API surface.
obsidian-cli
Use the Obsidian CLI to debug, inspect, and test Obsidian plugins during development. Covers plugin reloading, console inspection, runtime evaluation, and common debugging recipes for the gemini-scribe plugin.
gemini-api-dev
Use this skill when building applications with Gemini models, Gemini API, working with multimodal content (text, images, audio, video), implementing function calling, using structured outputs, or needing current model specifications. Covers SDK usage (google-genai for Python, @google/genai for JavaScript/TypeScript, com.google.genai:google-genai for Java, google.golang.org/genai for Go), model selection, and API capabilities.