1. Habit
  2. Skills
  3. Devboxes skill
namespacelabs · 2K installs

Devboxes skill
Runs by itself, pull request opened.

Tests run on a disposable devbox.

Install the Devboxes skill and make it a habit: follow https://gethabit.dev/skills/namespacelabs/devboxes.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

2K installs2 starsApache-2.0 licenceSource on GitHub ↗

Devboxes

by namespacelabs · 2K installs

The skill

Devboxes is a skill for developers who create, run, share and tear down Namespace devboxes with devbox or boxctl, for isolated Linux or macOS builds, remote tests, Docker hosts and shared devbox.so URLs.

Only when you ask.

The habit

Tests run on a disposable devbox.

↻ Runs by itselfpull request opened

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

pull request opened. Runs in Claude Code routine.

  • ↻ pull request opened
  • pull_request.opened

02

It checks its work

exit code and cleanup. If a check fails, it tries again.

  • ✓the run summary prints exit=0
  • ✓devbox exec ls shows the synced files
  • ✓boxctl task list shows no leftover markers
  • ✓devbox expire --force succeeds

03

It remembers

devbox run log. The next run reads it first: image and size that worked last time.

loops/devbox-test-run-loop/run-log.md

One run, step by step.
Then it stops.

Stop ruleStops after one test run per pull request, with one retry.

  1. 01

    Preflight

    Check NAMESPACE_DEVBOX_WORKSPACE_DIR, resolve devbox and run auth check-login, with devbox login if needed.

  2. 02

    Create the box

    Run devbox create with --ephemeral, an image from devbox image list and a fitting size.

  3. 03

    Ask on limits

    If plan limits block creation, run devbox list and ask the user which box to reuse or expire.

  4. 04

    Sync the tree

    Upload or tar the working tree, or apply a patch plus untracked files from git ls-files.

  5. 05

    Run the tests

    Upload a run script, chmod it and run it with devbox exec, logging to /workspaces/run.log.

  6. 06

    Fetch on failure

    Use devbox download for the log only when the summary shows a non-zero exit.

  7. 07

    Tear down

    Clear any boxctl task markers and run devbox expire --force.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Devboxes skill helps.

Use it when

  • ✓ Tests need more than your laptop
  • ✓ You need a macOS or Linux box
  • ✓ You share a dev server with teammates

Skip it when

  • – The task runs fine locally
  • – You do not use Namespace

Questions

Devboxes skill, answered.

Why sync untracked files?

The skill warns that git diff misses new files, so a patch sync can leave them behind.

Should I curl the devbox.so URL to test it?

No. The skill says those URLs need a signed-in session; check from inside the box.

How do I install the Devboxes skill?

Copy the prompt at the top into your agent. It installs the skill from namespacelabs/agent-skills and sets up the habit. Or run npx skills add namespacelabs/agent-skills --skill devboxes.

Is the Devboxes skill free?

Yes. It is published under Apache-2.0. Habit is free too.

Devboxes. Now as a habit.

Install the Devboxes skill and make it a habit: follow https://gethabit.dev/skills/namespacelabs/devboxes.md

  • Free
  • No account
  • Undo in one line

All namespacelabs skills →More ops skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by namespacelabs, published under Apache-2.0. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.