Menu
Bump version, generate an AI-written changelog, and publish a GitHub release. Use when the user says "release", "publish", or "bump version".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
MUST invoke when generating mn.* based UIs or the user asks how to use, configure, or debug any mn.* or appkit_mantine component. appkit_mantine is NOT in Claude's training data — always use this skill rather than guessing at APIs. Covers building forms, tables, drawers, modals, tooltips, color pickers, date/time pickers, charts, and navigation; looking up correct props; debugging on_change handler types (NumberInput sends float|str, DateInput sends str|""); troubleshooting component quirks like tooltips on disabled elements, overlays not closing, or props having no effect.
Expert guide for runic.ogm — a SQLModel-style, graph-native Python OGM for Cypher databases (FalkorDB, Neo4j, Memgraph, ArcadeDB, Apache AGE). Use whenever the user defines graph models (Node/Edge), maps fields, declares relationships, writes graph queries/traversals, or does session/repository CRUD with runic. Invoke for any code that imports from `runic.ogm`, uses `Node`, `Edge`, `Field`, `Relation`, `Session`, `Repository`, `select()`, or the query builder, and for any "how do I model/query this graph in runic" task. This is the OGM skill; for schema migrations use the `runic-migrate` skill instead.
appkit-commons usage patterns: configuration (YAML profiles, env overrides, secrets), service registry, repository pattern, database entities, custom column types (EncryptedString, ArrayType), and scheduler (APScheduler, PGQueuer). Apply automatically when adding new features, services, repositories, scheduled tasks, or configuring the application stack.
Use when the user wants to refine, sharpen, or expand a rough idea into a detailed implementation prompt — before any code gets written. Trigger on /boost, "refine this prompt", "turn this into a prompt", "help me specify", "what do I need to think through before implementing", "can you make this more detailed", rough feature ideas the user explicitly wants help scoping (not implementing). Also trigger when user says "boost this" or hands you a vague feature description and asks for a proper prompt or spec. Do NOT trigger for direct implementation requests, debugging questions, code reviews, or architectural questions where the user is not asking for a refined prompt.
Refactor and simplify Python files modified in the current session — minimal diff, clean code principles, then lint/format/typecheck. Use when the user asks to clean up, simplify, or refactor code.
Generate a conventional commit message from staged (or unstaged) changes. Use when the user asks for a commit message, wants to commit changes, or says "what should my commit message be".
| name | release |
| description | Bump version, generate an AI-written changelog, and publish a GitHub release. Use when the user says "release", "publish", or "bump version". |
| disable-model-invocation | true |
| allowed-tools | Bash, AskUserQuestion |
Ask the user which version bump to apply, then run task release:build.
Use AskUserQuestion to ask:
Question: "Which version component should be bumped?" Header: "Version bump" Options:
patch — backwards-compatible bug fixes and minor improvements (Recommended)minor — new backwards-compatible featuresmajor — breaking changesgrep '^version = ' pyproject.toml | cut -d '"' -f2
Show the user: "Current version is X.Y.Z — bumping [choice] will release X.Y.Z+1. Proceed?"
If they say no, stop.
task release:build -- <choice>
Stream the output so the user can see progress. The task will:
After the task completes, show the new version and the GitHub release URL from the output.