blaxel-ai/deploy-dev
.agents/skills/deploy-dev/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add blaxel-ai/sandbox deploy-devInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 9:02 PM1.8s1 file scanned
SKILL.md
- name:
- deploy-dev
- description:
- 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.
Deployment Phase
After the self-review passes and the PR is confirmed ready for human review, proceed to merge into develop and trigger the dev deployment.
Step 1: Merge into develop
Using git commands directly:
- Ensure the working tree is clean (
git status --porcelainmust be empty) - Save the current branch name:
git branch --show-current - Fetch latest from origin:
git fetch origin - Checkout develop:
git checkout develop - Pull latest develop:
git pull origin develop - Merge the feature branch into develop:
git merge <feature-branch> --no-edit - Push develop:
git push origin develop - Switch back to the feature branch:
git checkout <feature-branch>
If the merge fails with conflicts, do NOT abort. Instead, resolve conflicts interactively: for each conflicting file, show the user both sides of the conflict and ask which version to keep (or how to combine them). Once the user has provided input for every conflict, stage the resolved files, complete the merge commit, and continue with the deployment. Only abort if the user explicitly asks to cancel.
Step 2: Confirm deployment
Send a brief message confirming that the merge into develop succeeded and both the controlplane and infrastructure runs completed successfully, including the run URLs.
Related Skills
blaxel-ai/update-api-reference
development
VerifiedTrustedCommunity
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.
15SKILL.mdUpdated Apr 17, 2026
blaxel-ai/run-integration-tests
development
VerifiedTrustedCommunity
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.
15SKILL.mdUpdated Apr 17, 2026
blaxel-ai/run-e2e
development
VerifiedTrustedCommunity
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.
15SKILL.mdUpdated Apr 17, 2026
blaxel-ai/playwright-e2e
testing
VerifiedTrustedCommunity
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.
15SKILL.mdUpdated Apr 17, 2026