skills.rest
DavidLam-oss
DavidLam-ossCOMMUNITY
Explore all skills by this author →
GitHub

project-release

Automate versioning, validation, and deployment for Obsidian plugins.

283|45|Updated Jan 25, 2026
Search Tags:#automation#versioning#deployment#plugin#release#obsidian
One-click install
npx skills add https://github.com/DavidLam-oss/obsidian-wechat-converter --skill project-release-davidlam-oss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-release
Source: https://github.com/DavidLam-oss/obsidian-wechat-converter/tree/main/.agents/skills/project-release
Command: npx skills add https://github.com/DavidLam-oss/obsidian-wechat-converter --skill project-release-davidlam-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the complex, multi-step process of releasing new versions of an Obsidian plugin, ensuring consistency across version files, release notes, and deployment tags.

Core Features & Use Cases

  • Version Synchronization: Automatically coordinates updates across package.json, manifest.json, and versions.json.
  • Release Guardrails: Runs automated scans and tests to prevent broken builds or security risks before deployment.
  • Use Case: When preparing a new plugin update, use this Skill to validate your code, generate the release notes, and trigger the automated GitHub release workflow.

Quick Start

Use the project-release skill to initiate the release process for version 2.7.0 by validating the current branch and preparing the release notes.

Frequently Asked Questions about project-release

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

FAQPage Schema
How do I automate Obsidian plugin versioning across multiple configuration files?▼

Automated Obsidian plugin versioning synchronizes semantic version updates consistently across your package.json, manifest.json, and versions.json files to prevent manual misalignment during releases.

How does automated release validation work for Obsidian plugin deployment?▼

Automated release validation for Obsidian plugins works by running security scans and build tests to prevent broken deployments before triggering the CI/CD pipeline and artifact packaging.

What is the best way to generate release notes for an Obsidian plugin update?▼

The best way to generate release notes for an Obsidian plugin update is to use an automated workflow that validates your current branch and prepares structured changelog entries during version synchronization.

Can I trigger a GitHub release workflow for an Obsidian plugin without manual artifact packaging?▼

Yes, you can trigger an automated GitHub release workflow for Obsidian plugins that handles artifact packaging and deployment directly after ensuring manifest consistency and security scan compliance.

When do I need semantic versioning automation for my Obsidian plugin development?▼

You need semantic versioning automation for Obsidian plugin development when preparing a new update, ensuring release guardrails like code validation and manifest consistency are met before deployment.

Related Skills

Explore More Software Engineering Skills→
jscraikjscraik
8

release

Automate semantic versioning, Git tags, and crates.io publishing via `just release`.

Community
Advanced
Minara-AIMinara-AI
28

publish

Automate versioning, tagging, and release workflows for Rust binaries and VSCode extensions.

Official
Advanced
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced
yonatangrossyonatangross
217

release-management

Automate GitHub releases with semantic versioning and the gh CLI.

Community
Advanced