skills.rest
cbgbt
cbgbtCOMMUNITY
Explore all skills by this author →
GitHub

test-local-twoliter

Build the twoliter binary from local source and test kits with TWOLITER_DIR overrides.

5|12|Updated Nov 24, 2025
Search Tags:#testing#build#cargo#make#local#twoliter#kits
One-click install
npx skills add https://github.com/cbgbt/bottlerocket-forest --skill test-local-twoliter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-local-twoliter
Source: https://github.com/cbgbt/bottlerocket-forest/tree/main/skills/test-local-twoliter
Command: npx skills add https://github.com/cbgbt/bottlerocket-forest --skill test-local-twoliter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables developers to build twoliter from a local source and configure kits to use the locally built binary for testing changes before release.

Core Features & Use Cases

  • Build from local source to produce a release-ready twoliter binary.
  • Point dependent kits to the local twoliter binary for integrated testing.
  • Validate fixes and changes end-to-end within a forest grove before creating a PR.

Quick Start

Ensure a local twoliter checkout is present. Build the binary and update kit tests to use it:

  • Build twoliter locally: cd twoliter; cargo build --release
  • Test with kits: cd kits/bottlerocket-core-kit; make build TWOLITER_DIR=./twoliter/target/release
  • Iterate: re-build and re-test as changes are made.

Frequently Asked Questions about test-local-twoliter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build and test twoliter locally before creating a release?▼

To build and test twoliter locally, compile the binary using cargo build --release, then run make build with the TWOLITER_DIR environment variable pointing to your local release directory to validate changes end-to-end.

What does local end-to-end validation in a Bottlerocket forest grove involve?▼

Local end-to-end validation involves building the twoliter binary from local source and configuring dependent kits to use it, ensuring modifications work correctly within a Bottlerocket forest grove before release.

Do I need a Rust toolchain and local source checkout to test twoliter changes?▼

Yes, testing twoliter changes requires a local twoliter source checkout, an installed Rust toolchain, and local kit repositories to enable integrated building and validation using cargo and make commands.

How do I configure kits to use a locally built twoliter binary for testing?▼

Configure kits to use a locally built twoliter binary by running make build with the TWOLITER_DIR variable set to your local release directory, such as TWOLITER_DIR=./twoliter/target/release.

What's the best way to iterate on twoliter source and re-run kit tests?▼

The best way to iterate is to re-run cargo build --release after modifying source code, then re-execute make build with TWOLITER_DIR overrides in your kit directory to validate the updated changes.

Related Skills

Explore More Software Engineering Skills→
cbgbtcbgbt
5

build-variant-from-local-kits

Build a Bottlerocket variant image from locally published kits.

Community
Advanced
cbgbtcbgbt
5

update-twoliter

Update Bottlerocket repositories to a new Twoliter version with SHA256 checksums.

Community
Advanced
RediSearchRediSearch
6.2k

write-rust-tests

Automate Rust unit and integration tests with cargo test.

Official
Intermediate
opensage-agentopensage-agent
113

fuzz

Automate AFL++ fuzzing campaigns with custom mutators and crash extraction.

Official
Advanced