By ondrasek
Automated semantic versioning and GitHub releases from conventional commits
Install automated release workflow and commit validation in a repository. Use when user says "set up releases", "add auto-release", "configure CI releases", "install release workflow", or wants automated semantic versioning with conventional commits.
Preview the next release — shows version bump, categorized release notes, and non-conventional commits. Use when user says "release status", "what's next release", "preview release", "release notes", or wants to see what will be in the next version.
A collection of Claude Code plugins by ondrasek.
Add this marketplace to Claude Code:
/plugin marketplace add ondrasek/cc-plugins
Then install individual plugins:
/plugin install blueprint@cc-plugins
| Plugin | Description |
|---|---|
| blueprint | Quality methodology for Python, .NET, Rust, and Neovim Lua — analyzes your project and configures 9 dimensions of quality tooling (16 skills: 4 languages x setup/audit/update/explain) |
| github-issues | Intelligent GitHub issue management — natural language queries, codebase-aware creation, progressive refinement (epics → user stories) |
| github-releases | Intelligent GitHub release management — version detection, conventional commit analysis, release notes generation |
| git-auto-commit | Fail-fast cascade checker — enforces staging, version bumps, conventional commits, and push via Stop hook |
| auto-release | Automated semantic versioning and GitHub releases from conventional commits |
| obsidian-blueprint | Quality methodology for git-managed Obsidian vaults — analyzes vault structure and configures 7 dimensions of content quality (5 skills: setup/audit/update/explain/calendar) |
| calendar-access | Read-only calendar access — Google Calendar (gcalcli) and Microsoft 365 (Azure CLI + Graph API), with SessionStart hook for today's events (10 skills: setup/view/search/list-calendars + 6 shortcuts) |
| Script | Description |
|---|---|
| python-quality-gate | Fail-fast Python quality gate — 14 checks via Stop hook. Not a plugin due to Claude Code plugin hook bugs. Install as a project-level hook pointing to the canonical gist; the script self-updates via ETag. |
# Test a specific plugin against a target project
cd /path/to/target-project
claude --plugin-dir /path/to/cc-plugins/plugins/blueprint
Executes bash commands
Hook triggers when Bash tool is used
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub ondrasek/cc-plugins --plugin auto-releaseIntelligent GitHub release management for Claude Code via gh CLI
Configure review-snapshot hook for detecting test runners and capturing post-session snapshots. Detects technology stacks, finds test runners, writes config, and installs a Stop hook that captures changed files, diff stats, and test results after every Claude Code session.
Quality methodology for Python, .NET, Rust, and Neovim Lua projects
Intelligent GitHub issue management for Claude Code via gh CLI
Fail-fast cascade checker — enforces staging, conventional commits, and push via Stop hook
Semantic versioning management and automated release workflows
Release workflow tools - auto-versioning, release notes, changelog updates
DevsForge Enterprise Changelog Generator delivering comprehensive automated changelog generation, conventional commit parsing excellence, and semantic versioning automation that transforms release documentation from manual effort into intelligent, professional release management
External artifacts: commit, pull-request, release-tag, issue-create
Semantic version bumping for plugins with git tags and commits
When writing a git commit message. When task completes and changes need committing. When project uses semantic-release, commitizen, git-cliff. When choosing between feat/fix/chore/docs types. When indicating breaking changes. When generating changelogs from commit history.