test-local-twoliter
Build and test local changes to twoliter before releasing
Security Assessment
About test-local-twoliter
The 'test-local-twoliter' skill enables users to build and test local changes to the 'twoliter' binary before releasing it. This is especially useful when developing or modifying the 'twoliter' source code, as it allows for real-time testing and debugging of changes. By building the binary from the local source and configuring kits to use the locally-built version, users can validate modifications before making a pull request or releasing a new version. This process provides an efficient way to ensure that changes work as expected and that bugs or issues can be resolved during the development process.
FAQ
How do I test local changes to twoliter?
To test local changes, build 'twoliter' using the command 'cargo build --release' and configure your kit to use the locally built binary by setting the 'TWOLITER_DIR' environment variable.
What if my changes are not taking effect?
Make sure you ran 'cargo build --release' after making changes, and verify the 'TWOLITER_DIR' path is correct. Ensure the binary exists in the specified directory by running 'ls -lh ./twoliter/target/release/twoliter'.
What do I do if I encounter build errors in twoliter?
Run 'cargo check' to get detailed error messages, and use 'cargo clippy' to catch common issues. Additionally, 'cargo test' can be used to verify that the tests pass.
Can I revert back to the released version of twoliter?
Yes, to use the released version of twoliter, simply omit the 'TWOLITER_DIR' override when running the 'make build' command.
Install test-local-twoliter
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
cbgbt/bottlerocket-forest