ワンクリックでManusで任意のスキルを実行

nocobase-revision

スター42

フォーク10

更新日2026年6月9日 03:02

Use when building a NocoBase app with NocoBase skills or the nb CLI and you want to save a completed, meaningful milestone as a restorable revision.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

nocobase

nocobase/skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Goal

Create one restorable revision with nb revision create after a meaningful NocoBase app-building milestone has been completed and verified.

When To Use

Use after a verified, meaningful app-building step has been completed.
Create one revision per meaningful milestone, not after every small tweak.
Skip it if the user explicitly says not to create a revision.

Version control gate

You must run nb api pm list before any revision-related decision, output, or command in this skill.
You must inspect the plugin list for @nocobase/plugin-version-control.
Only when that plugin exists and enabled=true may you continue with any nb revision create flow.
If the plugin is missing, or present but enabled=false, you must stop immediately.
In that blocked case, do not run nb revision create.
In that blocked case, do not mention the plugin check, do not mention revision capability, do not mention that revision was skipped, and do not expose any related explanation to the user.
In that blocked case, produce no revision action and no revision-status disclosure. Treat it as a silent no-op and exit this skill.
This gate is absolute. No exception, no fallback, no user-facing disclosure.

Command

Base: nb revision create "<DESCRIPTION>"
Cross-env: nb revision create --env <env> --yes "<DESCRIPTION>"
Optional flags: --api-base-url <url>, --role <role>, --token <token>, -j, --json-output

Rules:

DESCRIPTION is required.
Prefer the current CLI env. Omit --env when it is not needed.
Only add optional flags when the user or runtime actually needs them.
If --env differs from the current env, confirm before adding --yes.
Treat nb revision create as an API-backed command. If it fails because of sandbox or network permission restrictions, you must request user approval for the required permission and then retry. Do not stop at the first sandbox-related failure.

Description Rules

Keep it concise, professional, and milestone-oriented.
Describe what was completed: page, collection, form, action, or workflow.
Reuse the user's wording if it is already good; otherwise expand it into one short natural phrase.
Keep it within the CLI limit of 2000 characters.
Avoid vague labels such as snapshot, backup, test, version 2, or timestamp-only text.
Do not include secrets, tokens, URLs, or credential fragments.

Examples:

Completed customer detail page, edit form, and submission workflow wiring
Completed supplier collection, request form, and approval workflow setup
完成客户台账、详情页与审批提交流程配置

Workflow

Run nb api pm list.
Inspect the plugin list for @nocobase/plugin-version-control and continue only if that plugin exists with enabled=true.
If the plugin is missing or disabled, stop as a silent no-op with no user-facing disclosure.
Before first use in the current task after the gate passes, run nb revision create --help and follow the live CLI help.
Confirm the upstream work is already verified.
Normalize DESCRIPTION into one concise completed-work summary.
Resolve env. If an explicit env differs from the current env, confirm before adding --yes.
Build exactly one nb revision create command with only the needed flags.
Execute it. If it fails because of sandbox or network permission restrictions, you must request user approval for the required permission and retry.
Report the final description, env, exact command, and key result lines.

Stop When

@nocobase/plugin-version-control is missing from nb api pm list
@nocobase/plugin-version-control is present but enabled=false
the description is empty after normalization
the completed milestone is still too vague to describe naturally
the explicit env differs from the current env and confirmation is missing
the upstream verification step is incomplete
the CLI reports auth, env access, or revision capability problems
the command still fails after the required sandbox or network permission retry

Rules:

If the stop reason is missing or disabled @nocobase/plugin-version-control, stop silently and disclose nothing revision-related to the user.
For all other stop reasons, follow the normal reporting rules in this skill.

Output Contract

Final response should include:

final DESCRIPTION
completed milestone context
target env
exact nb revision create command that was executed or proposed
defaults or assumptions that were applied
next manual check step

Silent gate exception:

If @nocobase/plugin-version-control is missing or enabled=false, return no revision-related user-facing output at all.

このリポジトリの他の Skills

同じリポジトリ

nocobase-ui-builder

nocobase/skills

DEFAULT entry point for NocoBase Modern UI authoring or tweaks: new pages, blocks, menu items, and localized edits to blocks, fields, actions, layouts, or reactions on an already-running app via backend flow-surfaces through nb api. Also handles AI employee / AI assistant action placement on UI surfaces. Hand off employee lifecycle work such as discovering, judging, creating, or configuring profile, prompt, model, skills, tools, or knowledge base to nocobase-ai-employee, then return for the UI write. Only hand off to nocobase-dsl-reconciler when the user explicitly asks for DSL, YAML, git, or cli push workflow. Does not handle ACL, data modeling, workflow orchestration, browser reproduction, page error postmortems, or non-Modern page navigation.

2026-07-1442

nocobase-workflow-manage

nocobase/skills

Use when users need to inspect, create, revise, enable, or diagnose NocoBase workflows through the `nb` CLI, including trigger selection, node-chain changes, version safety checks, and execution troubleshooting.

2026-07-1342

nocobase-plugin-development

nocobase/skills

Step-by-step playbook for developing a NocoBase plugin, covering scaffolding, server-side code (collections, APIs, ACL, migrations), client-side code (blocks, fields, actions, settings pages, routes, components), i18n, and verification. TRIGGER when: user asks to create, build, implement, or develop a NocoBase plugin, mentions 'NocoBase plugin', or describes a feature to be built as a NocoBase plugin. This skill contains NocoBase-specific conventions and templates that general coding cannot replicate — always invoke it instead of planning from scratch.

2026-07-0242

nocobase-utils

nocobase/skills

General-purpose NocoBase reference utilities covering cross-cutting topics such as evaluator engines, expression syntax, UID generation, and more. Use when you need authoritative reference information or reusable snippets that apply across multiple NocoBase features.

2026-06-2642

nocobase-notification-manage

nocobase/skills

Use when users need to configure, inspect, test, or troubleshoot NocoBase notification management, including in-app message channels, email SMTP channels, workflow notification nodes, and notification send logs.

2026-06-1442

nocobase-prototype-repro

nocobase/skills

Use when the task hands over a prototype to reproduce in NocoBase — an HTML file, an image, or a link, INCLUDING the published form "Build a NocoBase app — X … Match the layout and signature visuals of this reference prototype: <url>" — or when someone says a built page "doesn't match the prototype / looks monotone / is ugly". A prototype/URL being present is what triggers this skill, EVEN WHEN the same prompt also says "build an app" — the verb "build" does not cancel the prototype. Skip it only when there is NO prototype at all: a bare "build me a CRM/app" → nocobase-app- discipline; a one-field edit / rename → nocobase-ui-builder. It turns "here is the prototype, build it" into a faithful app — analyze prototype, native CRUD, the right native block per region, then a screenshot-vs-prototype visual loop. Native-first; JS only inside a native container; never a full-page JS block. Mechanics live in nocobase-ui-builder, nocobase-data-modeling, nocobase-app-discipline.

2026-06-1242

name	nocobase-revision
description	Use when building a NocoBase app with NocoBase skills or the nb CLI and you want to save a completed, meaningful milestone as a restorable revision.
argument-hint	"<description>" [--api-base-url <url>] [--env <env>] [--role <role>] [--token <token>] [--yes] [--json-output]
allowed-tools	shell, local file reads
owner	platform-tools
version	1.0.0
last-reviewed	"2026-05-26T00:00:00.000Z"
risk-level	medium

Goal

Create one restorable revision with nb revision create after a meaningful NocoBase app-building milestone has been completed and verified.

When To Use

Use after a verified, meaningful app-building step has been completed.
Create one revision per meaningful milestone, not after every small tweak.
Skip it if the user explicitly says not to create a revision.

Version control gate

You must run nb api pm list before any revision-related decision, output, or command in this skill.
You must inspect the plugin list for @nocobase/plugin-version-control.
Only when that plugin exists and enabled=true may you continue with any nb revision create flow.
If the plugin is missing, or present but enabled=false, you must stop immediately.
In that blocked case, do not run nb revision create.
In that blocked case, do not mention the plugin check, do not mention revision capability, do not mention that revision was skipped, and do not expose any related explanation to the user.
In that blocked case, produce no revision action and no revision-status disclosure. Treat it as a silent no-op and exit this skill.
This gate is absolute. No exception, no fallback, no user-facing disclosure.

Command

Base: nb revision create "<DESCRIPTION>"
Cross-env: nb revision create --env <env> --yes "<DESCRIPTION>"
Optional flags: --api-base-url <url>, --role <role>, --token <token>, -j, --json-output

Rules:

DESCRIPTION is required.
Prefer the current CLI env. Omit --env when it is not needed.
Only add optional flags when the user or runtime actually needs them.
If --env differs from the current env, confirm before adding --yes.
Treat nb revision create as an API-backed command. If it fails because of sandbox or network permission restrictions, you must request user approval for the required permission and then retry. Do not stop at the first sandbox-related failure.

Description Rules

Keep it concise, professional, and milestone-oriented.
Describe what was completed: page, collection, form, action, or workflow.
Reuse the user's wording if it is already good; otherwise expand it into one short natural phrase.
Keep it within the CLI limit of 2000 characters.
Avoid vague labels such as snapshot, backup, test, version 2, or timestamp-only text.
Do not include secrets, tokens, URLs, or credential fragments.

Examples:

Completed customer detail page, edit form, and submission workflow wiring
Completed supplier collection, request form, and approval workflow setup
完成客户台账、详情页与审批提交流程配置

Workflow

Run nb api pm list.
Inspect the plugin list for @nocobase/plugin-version-control and continue only if that plugin exists with enabled=true.
If the plugin is missing or disabled, stop as a silent no-op with no user-facing disclosure.
Before first use in the current task after the gate passes, run nb revision create --help and follow the live CLI help.
Confirm the upstream work is already verified.
Normalize DESCRIPTION into one concise completed-work summary.
Resolve env. If an explicit env differs from the current env, confirm before adding --yes.
Build exactly one nb revision create command with only the needed flags.
Execute it. If it fails because of sandbox or network permission restrictions, you must request user approval for the required permission and retry.
Report the final description, env, exact command, and key result lines.

Stop When

@nocobase/plugin-version-control is missing from nb api pm list
@nocobase/plugin-version-control is present but enabled=false
the description is empty after normalization
the completed milestone is still too vague to describe naturally
the explicit env differs from the current env and confirmation is missing
the upstream verification step is incomplete
the CLI reports auth, env access, or revision capability problems
the command still fails after the required sandbox or network permission retry

Rules:

If the stop reason is missing or disabled @nocobase/plugin-version-control, stop silently and disclose nothing revision-related to the user.
For all other stop reasons, follow the normal reporting rules in this skill.

Output Contract

Final response should include:

final DESCRIPTION
completed milestone context
target env
exact nb revision create command that was executed or proposed
defaults or assumptions that were applied
next manual check step

Silent gate exception:

If @nocobase/plugin-version-control is missing or enabled=false, return no revision-related user-facing output at all.