blaxel-ai
11 verified skills153 total stars
update-api-reference
Regenerate the OpenAPI reference documentation after adding, modifying, or removing API endpoints in sandbox-api. Run this whenever handler signatures, route paths, or swag annotations change.
development15
playwright-e2e
Deploy a Playwright sandbox (chromium or firefox) on Blaxel and run e2e tests against it. Use to validate that playwright hub images work end-to-end (browser connection, page navigation, DOM interaction) after changes.
testing15
run-integration-tests
Run the sandbox-api integration tests against a live API instance. Use after making changes to sandbox-api to verify all endpoints still work correctly.
development15
check-ci
Poll CI status on a branch until the "Build and Push Sandbox" workflow completes. Use after pushing to develop or any branch where you need to confirm the build succeeded before proceeding.
development15
add-hub-template
Create a new sandbox hub template (a pre-configured micro VM environment). Use when adding support for a new language, framework, or toolchain as a reusable sandbox image.
tools15
run-e2e
Run the full end-to-end test suite against a custom sandbox image deployed locally or on Blaxel. Use before merging significant changes to validate the complete sandbox-api binary, not just unit/integration tests.
development15
check-deploy
Watch CI until the "Build and Push Sandbox" workflow completes. For dev deployments, watches the develop branch. For prod deployments, watches the latest tag. Use after merging into develop or pushing a release tag.
development15
deploy-dev
Deploy the app to the dev environment. Use after a PR is marked as reviewable (ready for review) so reviewers can check out the changes running in dev.
development15
dev-environment
Start the local sandbox-api development environment with hot-reload. Use when developing or testing changes to the sandbox-api Go code locally.
development15
lint
Lint all changed Go files, fix every error, and confirm the build passes. Use when the user says "fix lint", "run lint", "lint", or when pre-commit hooks fail. Also use this proactively before committing code or when you notice linter warnings in build output.
development9
build-dev
Build the CLI in development mode. Use when the user says "build", "build dev", "compile", "rebuild", or when you need to test local changes to the CLI binary. Also use this after writing code changes to verify they compile correctly, or when the user wants to try out their changes locally.
tools9