Skill UI

This skill automates the generation of comprehensive changelogs and release notes directly from commit history, Pull Requests (PRs), and release tags. It ensures that documentation adheres to industry-standard formats, such as Keep a Changelog, streamlining release workflows and standardizing version management practices.

This skill automatically collects raw activity data (merged PRs, issues, commits, and optional Slack updates) from repositories. It formats this data using predefined templates, runs quality checks, and prepares a structured changelog draft. It can automatically commit the draft to a new branch and open a Pull Request (PR) for review, making it ideal for generating weekly or monthly release notes.

A powerful tool for comprehensive, offline dependency auditing across 8+ programming ecosystems (e.g., Node, Python, Go, Rust). It identifies critical CVE vulnerabilities, license conflicts, and calculates safe upgrade paths, making it essential for pre-release security checks, legal compliance reviews, and major version migrations.

This skill teaches the critical principles and decision-making processes for safe production releases. It covers platform selection (e.g., Kubernetes, Vercel), mandatory pre-deployment verification (Code Quality, Environment), structured workflows (Prepare, Backup, Deploy, Verify), and advanced strategies like Blue-Green and Canary deployments. Focuses on thinking through risk mitigation, not just executing scripts.

Coordinates a repeatable pre-PR or pre-release workflow for Django apps, covering environment validation, linting, formatting, migrations, tests with coverage, security scans, performance validation, and static asset readiness to ensure deployment confidence.

A comprehensive guide covering advanced traffic routing and management techniques within a service mesh using Istio. Learn how to implement critical deployment strategies like Canary releases and Blue-Green deployments, configure circuit breakers, manage retries, and perform fault injection testing. Includes YAML templates for VirtualService, DestinationRule, and Gateway setup, essential for reliable production service deployments.

This comprehensive workflow automates the core source-to-Lokalise process. Users can upload source translation files (JSON, XLIFF, PO, etc.), programmatically create new keys from code scans or CMS exports, update existing keys, and manage release tags. It is designed for CI/CD pipelines and bulk content synchronization.

A comprehensive guide for setting up Continuous Integration and Continuous Deployment (CI/CD) workflows for Obsidian plugins using GitHub Actions. This setup automates critical tasks like build validation on every push, manifest consistency checks, version number bumping, and structured GitHub releases, ensuring robust and reliable plugin deployment lifecycles.

A comprehensive guide for the full lifecycle release and distribution of Obsidian plugins. This skill covers all necessary steps, including building release assets, managing version bumps, creating GitHub releases, and submitting the required Pull Requests to the official Obsidian community plugin directory. Essential for developers launching or updating plugins.

This comprehensive checklist guides developers through the pre-release verification process for Obsidian community plugins. It covers critical technical areas such as validating manifest structure, ensuring clean production builds (e.g., removing sourcemaps), identifying potential memory leaks, and verifying cross-platform readiness, ensuring a high-quality user experience upon submission.

This guide provides essential, production-ready architectural patterns for building highly reliable Obsidian plugins. It addresses common development pitfalls such as managing typed settings with versioned migration, implementing safe vault operations (check-before-act), and handling event listeners to prevent memory leaks. Use these patterns when hardening your plugin for public release or refactoring for maximum stability.

A comprehensive guide for developers migrating and upgrading Obsidian plugins across major API versions. It covers critical steps such as auditing plugin compatibility, implementing version-aware settings migration logic (for user data persistence), replacing deprecated API calls (e.g., Vault, Editor, FileManager), and updating configuration files like manifest.json to ensure stability on new Obsidian releases.