01
It starts by itself
weekly drift check. Runs in Claude Code routine or GitHub Actions.
- ↻ weekly drift check
0 7 * * 1
Spec and code stay aligned.
Install the Weed skill and make it a habit: follow https://gethabit.dev/skills/juxt/weed.md
3K installs518 starsMIT licenceSource on GitHub ↗

Weed
by juxt · 3K installs
The skill
The weed skill compares Allium specifications with implementation code, finds where they diverged, classifies each divergence and helps resolve it, for teams that keep specs and code in sync.
Only when you ask.
The habit
Spec and code stay aligned.
↻ Runs by itselfweekly drift check
When does it start? How does it check its work? What does it remember?
Stops after one check pass over all specs per run; no edits in check mode.
Your agent reads the language reference and the .allium files, then runs allium check.
It finds the implementation for each entity, rule and trigger.
It flags what the spec says but code skips, and what code does that the spec omits.
It checks transition reachability, trigger coverage, undeclared transitions and invariant enforcement.
If available, allium analyse finds process gaps the comparison misses.
Each divergence gets a proposed class, and you confirm or override it.
It writes only in its own folder and asks you before anything goes out.
Read both lists. If the left one sounds like you, the Weed skill helps.
Only in update spec or update code mode. The default check mode changes nothing.
Spec bug, code bug, aspirational design or intentional gap.
Copy the prompt at the top into your agent. It installs the skill from juxt/allium and sets up the habit. Or run npx skills add juxt/allium --skill weed.
Yes. It is published under MIT. Habit is free too.
Install the Weed skill and make it a habit: follow https://gethabit.dev/skills/juxt/weed.md
All juxt skills →More code skills →
Works in
Made by juxt, published under MIT. Habit links to the original and never changes it. Is this your skill?