Skip to content
Skills Library
Programming · Building & coding

setup

/setup

Install and configure rllvm, or diagnose it when capture or a query fails. Use when the user wants to start using rllvm, when an rllvm command reports a missing tool or config, when no bitcode was captured, or when a tool rejects a captured module.

Repository
rllvm ↗
Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

95/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content30 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Install and configure rllvm, or diagnose it when capture or a query fails. Use when the user wants to start using rllvm, when an rllvm command reports a missing tool or config, when no bitcode was captured, or when a tool rejects a captured module.

Original author description

Install and configure rllvm, or diagnose it when capture or a query fails. Use when the user wants to start using rllvm, when an rllvm command reports a missing tool or config, when no bitcode was captured, or when a tool rejects a captured module.

How it works

  1. 1. Diagnose
  2. 2. Install what is missing
  3. 3. Choose the LLVM by what will read the bitcode
  4. 4. Configure
  5. 5. Verify
  6. Troubleshooting
Original SKILL.md headings · 88 lines, 592 words
SKILL.md preview
---
name: setup
description: Install and configure rllvm, or diagnose it when capture or a query fails. Use when the user wants to start using rllvm, when an rllvm command reports a missing tool or config, when no bitcode was captured, or when a tool rejects a captured module.
---

# Setting up rllvm

The scripts live at `${CLAUDE_SKILL_DIR}/../../scripts/doctor.sh` and
`${CLAUDE_SKILL_DIR}/../../scripts/smoke-test.sh`. Both are read-only; neither
writes a config or runs the user's build.

## 1. Diagnose

Run `${CLAUDE_SKILL_DIR}/../../scripts/doctor.sh`. It prints facts, `note:`
lines for optional pieces, `problem:` lines, and `problems: N`. Work from its
report, not from guesses.

## 2. Install what is missing

Ask before installing anything.

```bash
brew install h1994st/tap/rllvm llvm        # or: cargo install rllvm
brew install h1994st/tap/rllvm-query       # or: cargo install rllvm-query
```

The Homebrew `rllvm-query` brings its own LLVM; `rllvm-query --llvm-version`
reports which.

On Ubuntu/Debian, LLVM for capture comes from
`sudo apt install llvm llvm-dev clang libclang-dev`.

`cargo install rllvm-query` needs `LLVM_SYS_231_PREFIX` when `llvm-config` is
not on `PATH`. On Ubuntu/Debian, it also needs `libpolly-N-dev` alongside
`llvm-N-dev` and `libclang-N-dev`, with a matching major `N`.

## 3. Choose the LLVM by what will read the bitcode

A reader understands bitcode from its own LLVM major and older, never newer.
Readers include `rllvm-query`, `llvm-link` in the configured LLVM (which merges
Rust bitcode from `rustc`), and any analyser the user hands the module to
(PhASAR, SVF, KLEE). Capture with an LLVM no newer than the oldest reader.
`doctor.sh` flags the pairs it can see; ask about analysers it cannot.

## 4. Configure

The config is `$RLLVM_CONFIG`, else `~/.rllvm/config.toml`.

- **No config:** show `rllvm-init --dry-run`, then run `rllvm-init` with the
  same flags. `--llvm-prefix <dir>` picks a toolchain: the directory holding
  `bin/llvm-config`, such as `$(brew --prefix llvm)` or `/usr/lib/llvm-22`.
- **A config exists:** do not run `rllvm-init` over it — it rewrites the file
  and drops keys the user set by hand (`bitcode_store_path`, `cache_enabled`,
  `lto_mode`, …). Show `rllvm-init --dry-run`, and write only with the user's
  approval, carrying those keys across. Or write a separate file with
  `rllvm-init -o <path>` and set `RLLVM_CONFIG=<path>` for this project.

Any wrapper run with no config writes one from detection, so configure before
the first build.

Optional keys worth knowing, with the environment variable that overrides
each where one exists:

| Key | Effect | Override |
| --- | --- | --- |
| `bitcode_store_path` | one absolute directory for all bitcode | |
| `bitcode_root` | record bitcode paths relative to this root | `RLLVM_BITCODE_ROOT` |
| `lto_mode` | `marker` (default), `save-temps` or `skip` | `RLLVM_LTO_MODE` |
| `cache_enabled`, `cache_dir` | reuse validated bitcode (default off, `~/.rllvm/cache`) | `RLLVM_CACHE` |
| `query_cache`, `query_cache_warn_mb` | reuse rllvm-query's extracted per-module facts (default on, warns past 1024 MB) | `RLLVM_QUERY_CACHE` |
| `log_level` | 0 errors (default) up to 4+ trace | `RLLVM_LOG_LEVEL` |
| `llvm_objcopy_filepath` | embedding tool; needed for targets such as RISC-V | |
| `llvm_bindir` | absolute directory where `llvm-nm`, `llvm-dis` and `llvm-extract` are found; written by `rllvm-init` (default: `llvm-config --bindir`) | |
| `rustc_filepath` | the real `rustc` for `rllvm-rustc` | `RLLVM_REAL_RUSTC` |

## 5. Verify

Run `${CLAUDE_SKILL_DIR}/../../scripts/smoke-test.sh`: one `ok:` line per
step, `skip:` for optional pieces, and on failure `fail:` with the step's
output. Then run `doctor.sh` again and expect `problems: 0`.

## Troubleshooting

Start from `doctor.sh` every time.

| Symptom | Check |
| --- | --- |
| `rllvm-get-bc` finds no modules | the build used the wrappers: rerun one compile with `--rllvm-verbose=3`, or `RLLVM_LOG_LEVEL=3` under Cargo |
| A tool rejects the module | the capture LLVM is newer than that tool's; see step 3 |
| Modules reported missing | the build tree moved (build with `RLLVM_BITCODE_ROOT`, extract with `--bitcode-root`) or the bitcode was deleted |
| Stale results after a rebuild | `RLLVM_CACHE` is on and a side input preprocessing cannot see changed; rebuild with it off |

Versions

RepositoryScoreLicence
This page · h1994st/rllvm95Apache-2.0
HwangSlater/harness-fit100MIT
nesquikm/dev-process-toolkit100MIT
userKael/rastro100MIT
als-apg/osprey100BSD-3-Clause
dedujeong/gemba100Apache-2.0
eigenwise/eigenwise-toolshed100MIT
awrshift/agent-memory-kit100MIT
lifecycle-innovations-limited/claude-ops100MIT

Database snapshot: 13.11.2026 · package version 2e1e7cfb0d8e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100query
    Choose the rllvm-query tool that answers a question about a captured program, and report its answer without over-claiming. Use for questions about definitions, callers, callees, reachability, function pointers or external calls in captured bitcode, and every time an rllvm-query…
  • 90capture
    Capture LLVM bitcode from a project with rllvm and turn it into a catalog or module. Use when the user wants bitcode, a whole-program .bc, a catalog, or to analyze or query code that has not been captured yet — C, C++, Objective-C, Rust, mixed-language, cross-compiled, WebAssembly or eBPF.
  • 100bmad-loop-setup
    Sets up BMAD Loop Skills module in a project. Use when the user requests to 'install bmad-loop module', 'configure BMAD Loop Skills', or 'setup BMAD Loop Skills'.
  • 100dx-step-fix
    Diagnose and fix a blocked step — compile error, test failure, review rejection — directly or by adding corrective steps to implement.md. Use when /dx-step fails.
  • 100sample-module-setup
    Sets up BMad Samples module in a project. Use when the user requests to 'install samples module', 'configure BMad Samples', or 'setup BMad Samples'.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.