メニュー
Use liberally when you introduce, discover, or upgrade a third-party package or external service. Registers the dependency so future sessions know what the project relies on.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user's prompt is delivered outside the execution context of an existing Jumbo goal, the prompt is imbued with an objective that is not already defined as a Jumbo goal.
Use when a Jumbo-managed agent file tells the agent to bootstrap the session. Runs Jumbo's session router only when the agent has not already received a routed Jumbo command.
Use when an agent needs to discover Jumbo command syntax after session routing. Directs command discovery through CLI help instead of static command catalogs.
Use when implementation discovers durable project context that must be recorded in Jumbo. Captures decisions, components, dependencies, relations, guidelines, and invariants during the work.
Use when the user corrects an approach, constraint, workflow, or style. Converts corrections into Jumbo guidelines or invariants so future sessions receive the constraint.
Use when a Jumbo goal has been approved by QA review and needs architectural reconciliation before closing. Captures new learnings, updates stale entities, and ensures documentation reflects the work performed.
| name | jumbo-add-dependency |
| description | Use liberally when you introduce, discover, or upgrade a third-party package or external service. Registers the dependency so future sessions know what the project relies on. |
Register a third-party dependency with Jumbo when you add a new package, discover an unregistered one, or integrate with an external service.
Check for an existing dependency to avoid duplication. Consider renaming, updating, or deprecating and replacing a previously registered dependency before registering a new one.
Use the search subcommand to locate previously registered dependencies:
jumbo dependencies search -q <query>
jumbo dependency add \
--name "<Display name>" \
--ecosystem "<npm|pip|maven|service|...>" \
--package-name "<package-identifier>" \
--version-constraint "<semver-range>"
jumbo dependency add \
--name "testing lib" \
--ecosystem npm \
--package-name jest
Name does not match the package. Missing version constraint means future agents cannot detect version drift or compatibility issues.
jumbo dependency add \
--name "Jest" \
--ecosystem npm \
--package-name jest \
--version-constraint "^29.7.0"
Name matches the package identity. Ecosystem and package name enable automated lookups. Version constraint communicates the compatibility range.