Retroactive whole-repo bloat removal (spec H-2ii). Scores an existing repo on the deterministic bloat axes, writes BLOAT-REPORT.md, and — only behind a passing test-suite safety oracle — proposes gated refactor waves as a PR. The zero-risk adoption hook.
The first-five-minutes wow. Scaffolds a fully-specified canned task (a real Todo REST API + single-page frontend + tests + README) into a fresh project dir and hands you the exact command to watch Heimdall build it end-to-end. Safe by default (dry mode) — never auto-executes without --run. Use when demoing Heimdall to…
Bootstrap the designmatch skill in a React Native project from a Claude Design link. Auto-imports the Visual QA stub helper (visual-qa.ts), writes default state.vqa.json, registers the canonical source, updates .gitignore, and prints the wiring snippet. Use when starting visual-parity work on a new RN screen or when…
Overnight autoresearch + maintainer sweep that surfaces a MORNING REPORT — suggested changes, issues raised with fixes, and kept improvements. Shadow-first; never auto-pushes. Runs on-demand or scheduled for off-hours.
Submit team feedback as a GitHub issue on the repo, straight from an hmd session. Use when a team dev wants to flag friction, request a change, or report something about the team flow. Files the dev's words + minimal context (hmd version, optional command/phase) via the existing issue-loop GitHub connector — NO…
Print a ONE-COMMAND team join to recruit a teammate onto your Heimdall team. Use when a dev wants to add someone to their team's presence wall — the statusline "invite your team" tease points here. Resolves this repo's team secret from the dev's OWN /.heimdall/team.json and inlines it (plus the control-plane URL) into…
Run automated maintenance — seeker finds bugs from pod logs and raises GitHub issues, fixer picks them up and creates PRs. Can run as a one-shot or scheduled via /schedule.
File a GitHub issue against the Heimdall plugin repo from inside a session. Use when the user reports a bug, requests a feature, or wants to flag a docs/help-text problem in Heimdall itself. Auto-fills environment (plugin SHA, OS, recent commits) and posts to randomittin/heimdall (or the plugin's origin remote).…
Save current work state for next session. Creates/updates .planning/ files (CHECKPOINT.md, STATE.md, settings.json) so Heimdall resumes with full context. NOT a rewind — saves forward progress. Run before closing a session or at any milestone.
Show or change which offline coding-AI CLI backend hmd prefers (Claude Code, Cursor CLI, ...). Use with a letter, backend id, or loose name, or no argument to show current + detected options.
Manage this repo's TEAM for multi-tenant Heimdall presence — mint, join, or inspect the per-repo team secret. Use when a dev wants to start a private team, switch teams, join a teammate's team, or check which team this repo is on. A team = a high-entropy secret scoped to a repo; presence (HAID + online + edits) is…
Runs before the agent uses a tool for Bash, Read, Grep, Glob, Agent, Write, Edit, Edit, MultiEdit and Write tool calls, executing heimdall-stub-patterns.sh with --show-toplevel, ---, --task, --spec and --arg (5 commands). From randomittin/heimdall.
Runs after a tool call finishes for Bash, Write, Edit, MultiEdit, NotebookEdit, Write and Edit tool calls, running an inline shell check (3 commands). From randomittin/heimdall.
Runs when a session starts, executing build-tracker.sh with --show-toplevel, --apply, --advise, --repo and --session (8 commands). From randomittin/heimdall.
Use when matching a React Native screen to a Claude Design HTML canonical at ≥95% visual parity on real Android/iOS hardware — closes the loop with a VQA stub mode, Playwright canonical renderer at 1080×2444, and a dual-metric pixelmatch + SSIM diff harness producing composite triptychs.
The deliberate self-improvement loop for the maintainer — step back from fixing issues and improve Heimdall's OWN capability. Ports karpathy/autoresearch to Heimdall's routing/planning: collect evidence from metrics.jsonl + queue dead/done stats → form testable hypotheses → run a bounded routing experiment → evaluate…
Suggest whether the machine needs a DISK or MEMORY cleanup — and catch the case where Heimdall ITSELF is the hog (runaway orphaned python from the presence keeper). Use when the machine is slow / swapping / laggy, disk or "System Data" is full, memory is exhausted, at the start of a long session, or when the user asks…