caveman
Terse communication style
- License 许可
- MIT
- 最近更新
- 2026-11-09
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- new-bundle
- triggers
- [ "new-bundle", "new bundle", "scaffold project-local", "create project-local bundle", "project-local bundle", "new extension", "new addon", "new provider" ]
- namespace
- aiwg
- platforms
- [ "all" ]
- description
- Scaffold a project-local extension, addon, framework, plugin, or provider bundle under the configured AIWG artifact root.
03 SKILL.md 正文
New Bundle
Create a version-controlled project-local bundle under .aiwg/.
Behavior
-
Determine the bundle name and type.
-
Select an optional starter artifact.
-
Preview when requested, then run:
aiwg new-bundle <name> \ [--type extension|addon|framework|plugin|provider] \ [--starter skill|rule|agent|minimal] \ [--description "..."] \ [--dry-run] -
Deploy the completed bundle with
aiwg use <name>. -
Validate project-local health with
aiwg doctor. -
When the bundle is ready to graduate, use
aiwg promote <name> --dry-run.
The default type is extension; the default starter is skill. The aliases
new-extension, new-addon, new-framework, new-plugin, and new-provider
select their corresponding type.
Safety
- Use
--dry-runbefore scaffolding when the target or layout is uncertain. - Refuse to overwrite an existing bundle.
- Keep project-local source in version control; provider deployment copies are generated artifacts.
References
- @$AIWG_ROOT/src/cli/handlers/subcommands.ts —
new-bundlecommand handler - @$AIWG_ROOT/agentic/code/addons/aiwg-utils/skills/steward-quickref/SKILL.md
04 同仓库更多 Skills
worktree-lifecycle
Manage git worktrees for parallel development
verifier-loop
Run verifier loop until all checks pass
gitnexus-refactoring
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"
gitnexus-impact-analysis
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
gitnexus-guide
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"
gitnexus-exploring
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"