deploy-harness

Merge an approved improve branch into main and bump the plugin patch version.

3|Updated Apr 4, 2026

Search Tags:#git #release #version bump #plugin deployment #changelog hygiene #CI safety #branch merge

Ready to run

npx skills add https://github.com/crypdick/obsidian-knowledge --skill deploy-harness

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deploy-harness
Source: https://github.com/crypdick/obsidian-knowledge/tree/main/plugins/obsidian-knowledge/skills/deploy-harness
Command: npx skills add https://github.com/crypdick/obsidian-knowledge --skill deploy-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The deploy-harness skill solves the problem of releasing an approved harness improvement by reliably merging a prepared branch, version-bumping, and pushing an updated plugin to the main branch.

Core Features & Use Cases

Merges an approved improve-harness branch: Combines an improve/<slug> branch into main using a no-fast-forward merge to keep a clear history.
Bumps the plugin patch version: Updates .claude-plugin/plugin.json by incrementing the patch number without altering JSON formatting.
Publishes the release and cleans up: Pushes the updated main to origin and deletes the merged branch locally.

Quick Start

Ask the AI to deploy the approved branch improve/<slug> by running the release steps from within the obsidian-knowledge plugin repository.

Frequently Asked Questions about deploy-harness

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

FAQPage Schema

How do I safely merge an approved improvement branch into the main branch?▼

To safely merge an approved improvement branch, use a no-fast-forward merge to combine the prepared branch into main, preserving a clear commit history while stopping automatically on merge conflicts or uncommitted changes.

What is the best way to bump a plugin patch version before releasing?▼

The best way to bump a plugin patch version is updating the patch number in `.claude-plugin/plugin.json` during the release process, incrementing it without altering the existing JSON formatting before committing the release.

How do I deploy Obsidian plugin changes to production from a feature branch?▼

You can deploy Obsidian plugin changes by verifying the repository origin, merging the prepared feature branch into main, bumping the patch version, and pushing the updated main branch to origin to publish the release.

Can I release a patched plugin version if I have uncommitted local changes?▼

You cannot release a patched plugin version with uncommitted local changes. The deployment process stops automatically when it detects uncommitted changes or merge conflicts to ensure CI safety and repository hygiene.

Does the branch merge and release process clean up local feature branches?▼

Yes, the branch merge and release process deletes the merged feature branch locally after successfully pushing the updated main branch to origin, ensuring your local repository remains clean after deployment.

What happens if the repository origin does not match the target plugin during deployment?▼

If the repository origin does not match the target plugin, the deployment process requires verification before proceeding. This check ensures you are deploying the correct harness improvement to the intended Obsidian Claude Code plugin repository.