create-obsidian-release

Name: create-obsidian-release
Availability: InStock
Author: Discourse Graphs

Automate Discourse Graphs Obsidian plugin releases with GitHub pull request data.

44|7|Updated Oct 16, 2024

Search Tags:#automation #changelog #github #plugin #release #obsidian

Ready to run

npx skills add https://github.com/DiscourseGraphs/discourse-graph --skill create-obsidian-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-obsidian-release
Source: https://github.com/DiscourseGraphs/discourse-graph/tree/main/skills/create-obsidian-release
Command: npx skills add https://github.com/DiscourseGraphs/discourse-graph --skill create-obsidian-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tsx, gh, and includes scripts (resource) components.

What problem does it solve?

This skill automates the repetitive and error-prone process of generating release notes, categorizing pull requests, and publishing new versions of the Discourse Graphs Obsidian plugin.

Core Features & Use Cases

Automated Changelog Generation: Automatically filters merged pull requests to categorize features, bug fixes, and internal changes.
Release Orchestration: Handles the GitHub release lifecycle, including asset uploading and release note synchronization.
Communication: Drafts formatted Slack announcements to keep the community informed of new updates.

Quick Start

Run the create-obsidian-release skill with the version number 0.6.0 to generate the changelog and initiate the release process.

Frequently Asked Questions about create-obsidian-release

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

FAQPage Schema

How do I automate Obsidian plugin release notes and changelog generation?▼

Automate Obsidian plugin release notes by aggregating merged GitHub pull request data to categorize features, bug fixes, and internal changes. The workflow filters PRs to generate a structured changelog and handles versioning for the new release.

Do I need the GitHub CLI installed to automate plugin release workflows?▼

Yes, the GitHub CLI is required to automate the plugin release workflow. You need local environment configuration for repository access to aggregate pull request data, manage release assets, and synchronize release notes on GitHub.

Can I automatically categorize GitHub pull requests for release notes?▼

Yes, you can automatically categorize merged GitHub pull requests into features, bug fixes, and internal changes. This filtering mechanism aggregates PR data to generate structured changelogs and synchronize release notes.

What is the best way to notify a community about a new Obsidian plugin release?▼

Draft formatted Slack announcements to notify the community about a new Obsidian plugin release. The release orchestration handles asset uploading and synchronizes release notes before drafting the community notification.

How does release orchestration handle GitHub assets and versioning?▼

Release orchestration handles the GitHub release lifecycle by managing versioning, uploading release assets, and synchronizing generated release notes. It aggregates pull request data to automate the complete release process.

Why does my automated changelog generation require specific repository configuration?▼

Automated changelog generation requires specific local repository configuration to access GitHub pull request data via the GitHub CLI. Without proper environment setup, the workflow cannot filter merged PRs or manage release assets.