菜单
Project commit helper for corezoid-ai-plugin. Use instead of the generic commit skill whenever the user says "/commit", "commit", "закоммить", "сделай коммит", or asks to commit changes in this repository.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Universal Corezoid assistant. Use when the user asks anything about Corezoid processes, wants to work with process JSON files, mentions process nodes, MCP tools, process validation, or any Corezoid-specific task. Also use when the user mentions "Corezoid", "BPM process", "conv.json", "push process", "run task", or asks for general platform knowledge. This skill provides deep knowledge of the platform model and guides you to use the Corezoid MCP tools correctly.
Corezoid process creation specialist. Use when the user wants to create a new Corezoid process from scratch, build a new automation flow, design a new BPM process, or implement a new API connector. Activate when the user says "create a process", "build a new flow", "new process", "design from scratch", "implement a connector", "create an automation", or "add a new process".
Corezoid process editing specialist. Use when the user wants to modify, update, or fix an existing Corezoid process, add or remove nodes, change node behavior, add an API call, fix an error, or update process logic. Activate when the user says "edit a process", "modify", "update", "fix", "add a node", "change behavior", "add a call", "remove a node", or "update the logic".
Manages Corezoid environment variables (env_var) — create, list, modify, delete, and use variables in process JSON. Activate when the user mentions "variable", "env var", "environment variable", "secret", "create variable", "list variables", "delete variable", "modify variable", "env_var", "{{env_var", or asks how to store a URL, token, API key, or any constant that should not be hardcoded in a process. Also activate when a process references {{env_var[@name]}} and the variable does not exist yet.
Corezoid environment setup specialist. Use when the user wants to connect to Corezoid, set up credentials, authenticate, pull a project, configure the environment, or start working with a Corezoid project for the first time. Activate when the user says "init", "setup", "connect to corezoid", "login", "pull workspace", "configure environment", or "get started".
Auto-arrange the nodes of a Corezoid process into a clean, readable layout — a vertical top-to-bottom business flow with error handling railed off to the right and no overlapping nodes. Use it AUTOMATICALLY on every process YOU built or assembled, as the last step before push-process — never hand-place coordinates by eye (eyeballed grids overlap the moment nodes are taller than the step). Also reach for it whenever the user says a process is unreadable, tangled, ugly, a mess, or that nodes sit on top of each other, or asks to "arrange", "lay out", "tidy up", "make readable", "fix positions", "clean the diagram", "remove the overlaps" — or their equivalents in any language the user speaks. Do NOT silently re-arrange a process the user already positioned — see the "When you MAY re-layout" rules in the body. It only changes x/y coordinates and collapses IF/Delay/error nodes — never edges, logic, conv_id, aliases or node types.
| name | commit |
| description | Project commit helper for corezoid-ai-plugin. Use instead of the generic commit skill whenever the user says "/commit", "commit", "закоммить", "сделай коммит", or asks to commit changes in this repository. |
This project follows semver. Every commit must include a version bump in:
plugins/corezoid/.claude-plugin/plugin.json.claude-plugin/marketplace.jsonRun in parallel:
git diff HEAD — see what changedgit status — see untracked filesgit log -5 --oneline — see recent commit style| Change type | Bump |
|---|---|
| New feature, new tool, new skill, new node type | minor (2.3.x → 2.4.0) |
| Bug fix, doc update, text fix, refactor | patch (2.3.x → 2.3.x+1) |
| Breaking change, major redesign | major (2.x.x → 3.0.0) |
Read current version from plugins/corezoid/.claude-plugin/plugin.json.
Update the "version" field in both files to the new version:
plugins/corezoid/.claude-plugin/plugin.json.claude-plugin/marketplace.jsonPrepend a new entry at the top of CHANGELOG.md (right after the # Changelog heading) following the existing format:
## [<new_version>]
- <bullet summarising what changed — one line per logical change>
Derive the bullets from the staged diff: group related changes into a single readable line each. Keep it concise — one sentence per item.
Review the diff for changes that affect README content and update the relevant sections in README.md:
| What changed | What to update in README.md |
|---|---|
New or removed skill (SKILL.md added/deleted) | What it does table — add/remove the row |
| New or removed MCP tool | MCP Tools table — add/remove the row; Architecture code block if the tool group changes |
| New plugin directory or top-level file | Project structure code block |
| Breaking change to install/config | Installation or Configuration section |
If none of the above apply (e.g. pure bug fix, refactor, doc-only change inside an existing skill), skip this step — do not touch README.md.
Stage all modified files (including the two version files and CHANGELOG.md) and create a commit.
Follow the project's commit message convention:
<type>(<scope>): <short description>, bump to <new_version>
Types: feat, fix, docs, chore, refactor
End the commit message with:
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>