تشغيل أي مهارة في Manus بنقرة واحدة

commit

النجوم٥٧

التفرعات٨

آخر تحديث٢٥ مايو ٢٠٢٦ في ١٢:١٥

Project commit helper for simulator-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 ويثبّتها لك.

تشغيل في Manus

المصدر

corezoid

corezoid/simulator-ai-plugin

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name	commit
description	Project commit helper for simulator-ai-plugin. Use instead of the generic commit skill whenever the user says "/commit", "commit", "закоммить", "сделай коммит", or asks to commit changes in this repository.

Commit with auto version bump

This project follows semver. Every commit must include a version bump in:

plugins/corezoid/.claude-plugin/plugin.json
.claude-plugin/marketplace.json

Step 1 — Inspect changes

Run in parallel:

git diff HEAD — see what changed
git status — see untracked files
git log -5 --oneline — see recent commit style

Step 2 — Determine bump type

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.

Step 3 — Update versions

Update the "version" field in both files to the new version:

plugins/corezoid/.claude-plugin/plugin.json
.claude-plugin/marketplace.json

Step 3.5 — Update CHANGELOG.md

Prepend 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.

Step 3.6 — Update README.md

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.

Step 4 — Stage and commit

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>

المزيد من هذا المستودع

نفس المستودع

simulator-actors

corezoid/simulator-ai-plugin

Simulator.Company actor (record) specialist. Use when the user wants to create, update, read, search, or filter the *instances* of a form template (a.k.a. Account Template records) — i.e. data-bearing actors — and needs the `data` value protocol right. Activate when the user says "create an actor", "add a record", "create a record from this template", "fill in a form", "update actor data", "find actors where field = …", "filter actors by balance", "создай актор", "заполни шаблон", or "добавь запись". ALSO use this skill when the user asks what **processes / functions / Corezoid processes** an actor has or can call, or about an actor's **shared API keys / available functions** — call `getCorezoidProcesses`: "what processes/functions can this actor call", "actor's connected processes", "actor's API keys", "available functions of the actor", "які процеси/функції доступні актору", "процеси актора", "функції актора", "ключі доступу актора", "какие процессы/функции у актора", "процессы актора", "доступные функции а

2026-07-1557

simulator-graph

corezoid/simulator-ai-plugin

Simulator.Company graph structure specialist. Use when the user wants to build, edit, analyze, inspect, or ask questions about business process graphs, flowcharts, algorithms, actors (nodes), links (edges), or layers (visual views) in Simulator.Company. Trigger on any of these intents: — Creating: "create graph", "build flowchart", "new diagram", "add actor", "add block to graph", "create algorithm", "draw flowchart", "digital twin", "create process on graph", "build process diagram", "FlowchartBlock", "startStop", "predefinedProcess". — Editing: "edit graph", "update actor", "rename node", "change color", "move actor", "add step to flowchart", "modify diagram", "restructure process", "add edge", "remove link", "reorder steps", "update layer". — Syncing: "push graph", "pull graph", "sync graph", "push changes", "apply edits to layer". — Querying / analysis: "what actors are on this layer", "show me the graph", "who is connected to", "find actor", "list nodes", "describe the process", "analyze

2026-07-1557

simulator-styles

corezoid/simulator-ai-plugin

Simulator.Company Smart Form (CDU) STYLING specialist — authoring complex Less/CSS for Smart Forms: theme tokens, page/form/section layout, component re-skinning, reusable style patterns, responsive and design-system approaches. Use when the user wants to STYLE or RESTYLE an existing Smart Form / CDU app — change its look, build a theme, style a table / sidebar / modal / form, add a design system, fix spacing/colors/fonts, or apply a complex visual design. This skill owns the `style` / `styles/` layer; it reuses the Smart Form tools (pullSmartForm / pushSmartForm / deploySmartForm) but does NOT create form templates — for the data-schema form template use `simulator-forms`, and for page layout / viewModel / backend logic use `simulator-smart-forms` / `simulator-smart-forms-logic`. Activate on: "style a smart form", "CDU styles", "theme the form", "restyle", "custom CSS/Less for the app", "style the table/sidebar/modal/button", "design system for the smart form", "make it look like …", "застилізувати смартформ

2026-07-1457

simulator-forms

corezoid/simulator-ai-plugin

Simulator.Company form designer specialist. Use when the user wants to create or modify form templates (a.k.a. Account Templates / «Шаблон рахунків»), define custom field structures, set up account definitions, explore system forms, work with Smart Forms (CDU / Scripts), manage form status, or understand how forms define actor structure. Activate when the user says "create a form", "design a template", "add fields to form", "Account Template", "Шаблон рахунків", "define actor schema", or "what system forms are available".

2026-07-1057

simulator-agents

corezoid/simulator-ai-plugin

Simulator.Company digital-twin & actor-agent specialist — talk to an agent AS an agent and delegate work to it. An agent is ANY actor whose `description` holds an "# Agent" competency profile (what it does, what it knows, whether it fits a task). The common case is a person: every workspace user has a 1:1 twin actor (`systemObjType="user"`) carrying that profile. But any actor can be an agent — a service/bot twin, a team or department, an organization, a process. This skill discovers the agent (`findAgent`), loads its profile (`getAgent`), adopts it as the persona, then either does the task, finds a better-suited agent, or hands the decision to the user (for a person: a task or a p2p message; for a non-person: propose another executor or run/trigger it as an actor). It is the actor-analog of `simulator-skills` (the `Skills`-form registry), but the registry is the workspace's agent actors. Use when the user wants to "delegate", "assign this to <someone/something>", "can <X> do this", "who/what should do this",

2026-07-0857

simulator-chat

corezoid/simulator-ai-plugin

Simulator.Company chat & messaging specialist — sending messages to a user, and creating or reusing p2p (1:1) and group chats. In Simulator a chat is an actor of the Events system form (data.chatType = "p2p" | "group"), its participants are the actor's access-rule members, and its messages are `comment` reactions. Use when the user wants to "message", "write to", "DM", "send a message to" someone, "open a chat with", "start a conversation", or "reply in the chat". Activate on "write a message to user N", "send N a message", "open a chat with", "message someone", "напиши повідомлення користувачу", "надішли повідомлення", "відкрий чат з", "почни розмову з", "напиши юзеру", "напиши сообщение пользователю", "отправь сообщение", "открой чат с", "напиши в чат". For comments/approvals on an arbitrary actor (not a chat) use `simulator-reactions`; for files use `simulator-attachments`; for sharing/access in general use `simulator-access`.

2026-07-0757

name	commit
description	Project commit helper for simulator-ai-plugin. Use instead of the generic commit skill whenever the user says "/commit", "commit", "закоммить", "сделай коммит", or asks to commit changes in this repository.

Commit with auto version bump

This project follows semver. Every commit must include a version bump in:

plugins/corezoid/.claude-plugin/plugin.json
.claude-plugin/marketplace.json

Step 1 — Inspect changes

Run in parallel:

git diff HEAD — see what changed
git status — see untracked files
git log -5 --oneline — see recent commit style

Step 2 — Determine bump type

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.

Step 3 — Update versions

Update the "version" field in both files to the new version:

plugins/corezoid/.claude-plugin/plugin.json
.claude-plugin/marketplace.json

Step 3.5 — Update CHANGELOG.md

Prepend 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.

Step 3.6 — Update README.md

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.

Step 4 — Stage and commit

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>