How do I install the Dev Cycle skill?

Run npx skillmds@latest add xberg-io/dev-cycle in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dev Cycle safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dev Cycle?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dev Cycle free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dev Cycle?

xberg-io (@xberg-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dev Cycle by xberg-io — Agent Skill

Name: Dev Cycle
Author: xberg-io

Dev Cycle

Crawlberg iteration loops codified as Taskfile tasks — alef install/generate/format/bump, core and binding builds, e2e generate/build/test cycles, cleanup tiers, and the mock-server / stale-.so / precompiled-NIF / generated-e2e gotchas. Load when running or debugging crawlberg build, alef regeneration, or e2e workflows, or when unsure which task to run.

xberg-io cf9a5a4 2.3 KB Updated Sep 17, 2026

File contents

Iteration loops are codified as Taskfile tasks. Prefer them over ad-hoc commands.

After alef changes

task alef:install              # cargo install --path ../alef/crates/alef-cli
task alef:generate             # alef all --clean --format=false
task alef:format               # explicit Alef formatting; task format excludes this
VERSION=0.15.30 task alef:bump # bump pin in alef.toml + reinstall + regen

After crawlberg-core changes

task build          # core-only
task build:bindings # all bindings
task build:all      # core + all bindings

E2E cycles

task e2e:generate # regenerate all language test suites from fixtures
task e2e:build    # build bindings and the generated mock-server for e2e
task e2e:test     # run generated e2e suites
task e2e:all      # generate + build + run generated e2e suites

Cleanup

task clean           # per-language artifacts
task clean:workspace # cargo target + alef IR cache + legacy mock-server bins
task clean:e2e       # venvs, node_modules, _build, lockfiles, vendor/
task clean:full      # all of the above

Gotchas (codified, but worth knowing)

Two mock-server binaries. tools/mock-server is legacy/unused; e2e/rust/src/main.rs is alef-generated and the binary all language conftests actually spawn. task e2e:build builds the right one at e2e/rust/target/release/mock-server.
Python venv stale .so. After task python:build:dev, the e2e venv at e2e/python/.venv keeps a stale extension. task python:cycle runs uv sync --reinstall to refresh.
Elixir precompiled NIF. Rustler's precompiled binary is tagged at the package's release version and lags local source. CRAWLBERG_BUILD=1 is set in .task/languages/elixir.yml::e2e:test so the e2e suite always builds the NIF from local source.
Generated e2e files. e2e/<lang>/ is alef-generated — never hand-edit. Modify fixtures or alef codegen, then task alef:generate.

---name: dev-cycledescription: Crawlberg iteration loops codified as Taskfile tasks — alef install/generate/format/bump, core and binding builds, e2e generate/build/test cycles, cleanup tiers, and the mock-server / stale-.so / precompiled-NIF / generated-e2e gotchas. Load when running or debugging crawlberg build, alef regeneration, or e2e workflows, or when unsure which task to run.---Iteration loops are codified as Taskfile tasks. Prefer them over ad-hoc commands.### After alef changes```texttask alef:install # cargo install --path ../alef/crates/alef-clitask alef:generate # alef all --clean --format=falsetask alef:format # explicit Alef formatting; task format excludes thisVERSION=0.15.30 task alef:bump # bump pin in alef.toml + reinstall + regen```### After crawlberg-core changes```texttask build # core-onlytask build:bindings # all bindingstask build:all # core + all bindings```### E2E cycles```texttask e2e:generate # regenerate all language test suites from fixturestask e2e:build # build bindings and the generated mock-server for e2etask e2e:test # run generated e2e suitestask e2e:all # generate + build + run generated e2e suites```### Cleanup```texttask clean # per-language artifactstask clean:workspace # cargo target + alef IR cache + legacy mock-server binstask clean:e2e # venvs, node_modules, _build, lockfiles, vendor/task clean:full # all of the above```### Gotchas (codified, but worth knowing)- **Two mock-server binaries.** `tools/mock-server` is legacy/unused; `e2e/rust/src/main.rs` is alef-generated and the binary all language conftests actually spawn. `task e2e:build` builds the right one at `e2e/rust/target/release/mock-server`.- **Python venv stale `.so`.** After `task python:build:dev`, the e2e venv at `e2e/python/.venv` keeps a stale extension. `task python:cycle` runs `uv sync --reinstall` to refresh.- **Elixir precompiled NIF.** Rustler's precompiled binary is tagged at the package's release version and lags local source. `CRAWLBERG_BUILD=1` is set in `.task/languages/elixir.yml::e2e:test` so the e2e suite always builds the NIF from local source.- **Generated e2e files.** `e2e/<lang>/` is alef-generated — never hand-edit. Modify fixtures or alef codegen, then `task alef:generate`.

Frequently asked questions