// This skill should be used when the user wants to "use Alire", "install Alire","create an Alire project", "add a crate", "set up tests for an Alire crate", "add AUnit / GNATtest to an Alire project", or otherwise refine the crate structure of an Ada project
This skill should be used when the user wants to "fuzz Ada code", "run gnatfuzz", "generate a fuzzing harness", "investigate a fuzz crash", "write a fuzzing wrapper for an unsupported parameter type", "generate or minimize a corpus", or is otherwise running a fuzzing campaign on an Ada/SPARK project. Covers running gnatfuzz, designing fuzzable subprograms, managing corpora, and reading fuzzing outputs and crash files.
This skill should be used when the user wants to "prove SPARK code", "run GNATprove", "investigate unproved checks", "write contracts or invariants", "add loop invariants", "write ghost code or lemmas", or is working on SPARK formal verification. Covers running gnatprove, writing SPARK (contracts, types, loops, ghost code), and conducting proof campaigns.
This skill should be used when the user wants to "generate unit tests", "run gnattest", "create test skeletons", "build a test harness", "write AUnit tests", "add tests to Ada code", "run a testing campaign", or is otherwise working with GNATtest for Ada unit testing.
| name | alire |
| description | This skill should be used when the user wants to "use Alire", "install Alire","create an Alire project", "add a crate", "set up tests for an Alire crate", "add AUnit / GNATtest to an Alire project", or otherwise refine the crate structure of an Ada project |
| license | Apache-2.0 |
| metadata | {"version":"0.1.0"} |
Check whether alr is available:
alr --version 2>/dev/null || ~/.local/bin/alr --version 2>/dev/null
If Alire is NOT installed, ask the user if they would like you to install Alire for them.
If the user says "no", direct the user to visit "https://alire.ada.dev/" and stop.
If the user says "yes", follow the instructions in installing-alire to install Alire.
Note: alr has comprehensive built-in help. At any point, alr --help lists all available subcommands and alr --help` gives full usage details. Consult these whenever the reference files don't fully address the situation.
| Alire Command | Description | Reference |
|---|---|---|
| — | Install Alire | installation.md |
alr search | Search for crates in the index | alire-search.md |
alr toolchain | Inspect or pin compiler toolchains (optional — alr init/alr build auto-install default toolchain on first use) | alire-toolchain.md |
alr get | Fetch a crate from the index | alire-get.md |
alr with | Add a dependency | alire-with.md |
alr pin | Pin a dependency to a local path or Git repo | alire-pin.md |
alr install | Install a binary-tool crate to a shared prefix | alire-install.md |
alr build | Build the project | alire-build.md |
alr run | Run the project | alire-run.md |
alr exec | Execute a command in the project environment | alire-exec.md |
alr printenv | Print environment variables | alire-printenv.md |
| — | Set up tests for a crate (AUnit, GNATtest) | testing.md |
| — | Cross-compile for Raspberry Pi Pico | raspberry-pi-pico.md |
| — | Cross-compile for Zephyr (Arm / RISC-V) | zephyr.md |
Commands Not in the Reference Chart
If the user requests an alr workflow not covered above:
alr --help to confirm the subcommand existsalr <subcommand> --help to read its full usage