Menu
Build a variant using locally published kits for development validation
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/cbgbt/bottlerocket-forest --skill build-variant-from-local-kitsThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Edit Bottlerocket RPM spec files following project style conventions
Transform a rough plan into implement-commit ready artifacts. Allows rigorous review while implementing.
Implement commits from an implementation plan using a TDD pipeline
Based on SOC occupation classification
Showing SKILL.md
| name | build-variant-from-local-kits |
| description | Build a variant using locally published kits for development validation |
Build a complete Bottlerocket variant image using kits published to the local development registry. This enables end-to-end testing of kit changes before publishing to production registries.
build-kit-locally skill)cd ./bottlerocket
brdev twoliter use-local-deps
This creates Twoliter.override pointing to the local registry for fetching kits.
Edit Twoliter.toml and set vendor = "local" for kits you want from the local registry:
[kit.bottlerocket-core-kit]
vendor = "local" # Fetch from local registry
version = "2.0.0"
[kit.bottlerocket-kernel-6.1-kit]
# No vendor override - uses upstream
version = "2.0.0"
Only kits with vendor = "local" will be fetched from the local registry; others use upstream.
./tools/twoliter/twoliter update
cargo make
For specific variant:
cargo make -e BUILDSYS_VARIANT=aws-k8s-1.31
For specific architecture:
cargo make -e BUILDSYS_ARCH=aarch64
ls -lh build/images/*.img
The build should complete successfully and produce an .img file in build/images/.
When done testing, restore upstream configuration:
brdev twoliter use-upstream-deps
This removes Twoliter.override.
Remember to also revert any vendor = "local" changes in Twoliter.toml.
Kit not found in registry:
Error: failed to pull kit
Solution: Verify kit is published with brdev registry list
Version mismatch:
Solution: Ensure Twoliter.toml version matches the published kit version
Lock file out of sync:
Solution: Run ./tools/twoliter/twoliter update again