obsidian-ci-integration
Set up GitHub Actions CI/CD for Obsidian plugin development. Use when automating builds, tests, and releases for your plugin, or setting up continuous integration for Obsidian projects. Trigger with phrases like "obsidian CI", "obsidian github actions", "obsidian automated build", "obsidian CI/CD".
Install
mkdir -p .claude/skills/obsidian-ci-integration && curl -L -o skill.zip "https://mcp.directory/api/skills/download/8166" && unzip -o skill.zip -d .claude/skills/obsidian-ci-integration && rm skill.zipInstalls to .claude/skills/obsidian-ci-integration
About this skill
Obsidian CI Integration
Overview
GitHub Actions workflows for Obsidian plugin development: build validation on every push, automated releases when you tag, version-bump scripting, manifest.json validation, and BRAT beta channel support.
Prerequisites
- GitHub repository with an Obsidian plugin
- Working local build (
npm run buildproducesmain.js) manifest.jsonandversions.jsonin repo root- GitHub Actions enabled on the repository
Instructions
Step 1: Create Build Workflow
# .github/workflows/build.yml
name: Build Plugin
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 18
- name: Install dependencies
run: npm ci
- name: Build plugin
run: npm run build
- name: Verify build output
run: |
if [ ! -f main.js ]; then
echo "ERROR: main.js not found after build"
exit 1
fi
echo "main.js size: $(wc -c < main.js) bytes"
- name: Validate manifest.json
run: |
node -e "
const m = require('./manifest.json');
const required = ['id', 'name', 'version', 'minAppVersion', 'description', 'author'];
const missing = required.filter(f => !m[f]);
if (missing.length) {
console.error('Missing manifest fields:', missing.join(', '));
process.exit(1);
}
console.log('manifest.json valid:', m.id, 'v' + m.version);
"
Step 2: Create Release Workflow
# .github/workflows/release.yml
name: Release Plugin
on:
push:
tags:
- '*'
jobs:
release:
runs-on: ubuntu-latest
permissions:
contents: write
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 18
- run: npm ci
- run: npm run build
- name: Create GitHub Release
uses: softprops/action-gh-release@v2
with:
files: |
main.js
manifest.json
styles.css
draft: false
generate_release_notes: true
Step 3: Create Version Bump Script
// version-bump.mjs
import { readFileSync, writeFileSync } from 'fs';
const targetVersion = process.env.npm_package_version;
// Update manifest.json
const manifest = JSON.parse(readFileSync('manifest.json', 'utf8'));
const { minAppVersion } = manifest;
manifest.version = targetVersion;
writeFileSync('manifest.json', JSON.stringify(manifest, null, '\t'));
// Update versions.json — maps plugin version to minimum Obsidian version
const versions = JSON.parse(readFileSync('versions.json', 'utf8'));
versions[targetVersion] = minAppVersion;
writeFileSync('versions.json', JSON.stringify(versions, null, '\t'));
console.log(`Bumped to ${targetVersion} (minAppVersion: ${minAppVersion})`);
Step 4: Wire Version Bump into package.json
{
"scripts": {
"build": "node esbuild.config.mjs",
"dev": "node esbuild.config.mjs --watch",
"version": "node version-bump.mjs && git add manifest.json versions.json"
}
}
Now npm version patch (or minor/major) runs the bump script automatically.
Step 5: Add Manifest Validation Workflow
# .github/workflows/validate.yml
name: Validate Plugin
on: [push, pull_request]
jobs:
validate:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Check manifest/versions consistency
run: |
node -e "
const manifest = require('./manifest.json');
const versions = require('./versions.json');
const pkg = require('./package.json');
let fail = false;
if (manifest.version !== pkg.version) {
console.error('Version mismatch: manifest=' + manifest.version + ' package=' + pkg.version);
fail = true;
}
if (!versions[manifest.version]) {
console.error('versions.json missing entry for ' + manifest.version);
fail = true;
}
if (fail) process.exit(1);
console.log('All versions consistent: ' + manifest.version);
"
Step 6: BRAT Beta Support
Add a beta-manifest.json for BRAT beta testers:
{
"id": "your-plugin-id",
"name": "Your Plugin (Beta)",
"version": "1.2.0-beta.1",
"minAppVersion": "1.5.0",
"description": "Beta channel — install via BRAT",
"author": "Your Name"
}
Beta users install via BRAT by entering your GitHub repo URL. BRAT fetches the latest release (including pre-releases) automatically — no submission to the community repo needed.
Output
.github/workflows/build.yml— validates build on every push/PR.github/workflows/release.yml— creates GitHub release withmain.js,manifest.json,styles.csson tag push.github/workflows/validate.yml— checks version consistency across manifest, package.json, and versions.jsonversion-bump.mjs— keeps manifest.json and versions.json in sync with package.json version- Optional
beta-manifest.jsonfor BRAT beta channel
Error Handling
| Error | Cause | Solution |
|---|---|---|
main.js not found | Build script doesn't output to root | Check esbuild outfile points to ./main.js |
| Release has no assets | Tag pushed before build | Let the release workflow handle the build, don't attach manually |
| Version mismatch | Forgot npm version | Run npm version patch instead of editing manifest by hand |
| BRAT not picking up beta | No pre-release on GitHub | Create release and check "pre-release" checkbox |
npm ci fails | No lockfile | Commit package-lock.json to the repo |
| Permission denied on release | Missing contents: write | Add permissions block to release job |
Examples
Tag and Release a New Version
set -euo pipefail
# Bump, commit, tag, push — release workflow fires automatically
npm version patch
git push origin main --tags
Manual Build Verification
set -euo pipefail
npm ci
npm run build
test -f main.js && echo "Build OK: $(wc -c < main.js) bytes" || echo "FAIL: main.js missing"
node -e "const m=require('./manifest.json'); console.log(m.id, 'v'+m.version)"
Release with Changelog
# In release.yml, replace generate_release_notes with a body:
- name: Create GitHub Release
uses: softprops/action-gh-release@v2
with:
files: |
main.js
manifest.json
styles.css
body: |
## Changes
- Feature: Added X
- Fix: Resolved Y
Resources
- Obsidian Plugin Releasing Guide
- GitHub Actions Documentation
- BRAT Plugin
- softprops/action-gh-release
Next Steps
For publishing to the community plugin directory, see obsidian-deploy-integration.
For pre-release quality checks, see obsidian-prod-checklist.
More by jeremylongshore
View all skills by jeremylongshore →You might also like
flutter-development
aj-geddes
Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.
drawio-diagrams-enhanced
jgtolentino
Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.
ui-ux-pro-max
nextlevelbuilder
"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
nano-banana-pro
garg-aayush
Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.
fastapi-templates
wshobson
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
Related MCP Servers
Browse all serversExtend your developer tools with GitHub MCP Server for advanced automation, supporting GitHub Student and student packag
Optimize your codebase for AI with Repomix—transform, compress, and secure repos for easier analysis with modern AI tool
Empower AI with the Exa MCP Server—an AI research tool for real-time web search, academic data, and smarter, up-to-date
Enhance your Obsidian workflow with this plugin using Local REST API for advanced search, note access, and vault structu
Enhance your workflow with Obsidian Advanced, the ultimate Obsidian plugin for note management, automation, and advanced
GitHub Actions Trigger enables seamless integration to trigger workflows, fetch action details, and retrieve releases vi
Stay ahead of the MCP ecosystem
Get weekly updates on new skills and servers.