| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 26 天前 | ||
| 1 个月前 | ||
| 26 天前 | ||
| 26 天前 | ||
| 26 天前 | ||
| 1 个月前 | ||
| 26 天前 | ||
| 1 个月前 | ||
| 1 个月前 |
CANNBot npm installer
This directory is the complete npm project for @cannbot-plugin/cannbot.
npx @cannbot-plugin/cannbot install ops-direct-invoke --tool opencode
npx @cannbot-plugin/cannbot install ascendc-st-design --tool codex
The package build reads plugin definitions from ../plugins/ and Skill sources from the ../vendor/cannbot-skills submodule. prepack assembles the selected source trees into dist/plugins/, so npm users receive a self-contained package and never clone the source repository.
npm test
npm run build:plugins
npm pack --dry-run
npm run pack:smoke
npm publish --access public
npm publish runs the full test suite and installs the generated tarball through
its cannbot npm bin before publishing. Version 1.3.2 was released on 2026-08-31.
The npm package is a mixed-license distribution. The installer implementation
is MIT licensed. Assembled official plugins and bundled Skills retain the CANN
Open Software License Agreement Version 2.0 and any license notices included
with their content; see the package LICENSE overview and the license files in
each dist/plugins/<plugin>/ directory.
All clients use the same Node installer. Each source init.sh forwards the selected plugin, source repository, tool, and target to the CLI, which links Skills to the submodule. npm installation copies the bundled Skills. Plugin-specific dependency repositories are declared in plugin-install.json.
See the workflow installation and usage guide for all supported commands and prompt examples.
Community plugins with a plugin-sources.json are also assembled into the package. To install ops-direct-invoke from its source directory:
node script/bin/cannbot.js install ops-direct-invoke --source "$PWD" --plugin-dir plugins-community/ops-direct-invoke-harness --tool codex --target /absolute/project
--override-skills /absolute/overrides replaces selected existing repo-* Skills from same-named directories. Document templates are maintained under ops-direct-invoke/templates/docs; assembled workflow templates live in templates/workflows and are listed with usage conditions in templates/workflows/registry.yaml. The workflow entry and scheduler cannot be replaced through this option. See the ops-direct-invoke README for its task assembly rules and current public-interface limitations.
--plugin-dir selects a specific plugin directory when its folder name differs from its manifest name. Relative paths resolve from --source for source installs, or the installer package root for packaged installs. The requested install ID must match the manifest; installed assets and registry records always use that ID.