alire

Files (16)

• SKILL.md
• alire-build.md · references/
• alire-exec.md · references/
• alire-get.md · references/
• alire-init.md · references/
• alire-install.md · references/
• alire-pin.md · references/
• alire-printenv.md · references/
• alire-run.md · references/
• alire-search.md · references/
• alire-toolchain.md · references/
• alire-with.md · references/
• installation.md · references/
• raspberry-pi-pico.md · references/
• testing.md · references/
• zephyr.md · references/

SKILL.md (first lines)

> **OpenCode Paradigm (Ada/SPARK-First)**: This project uses Ada/SPARK as the primary
> implementation language.  All business logic, classification, gating, and state management
> MUST be in Ada/SPARK (SPARK_Mode => On).  Python is FFI-only (wrapper).  JavaScript is
> BANNED (TypeScript only for OpenCode plugin host API).  The frontend/UI remains identical
> in appearance but is driven by Ada/SPARK backend logic via FFI.  Validation: `gnatprove --level=4`,
> `pyrefly check .`, `ruff check .`, `jslint`.  Approval gates required before execution.
> Context must be loaded before any code changes.  See `ecc_adapter/` for the verified core.



# Alire Package Management Skill

## Prerequisites

Check whether `alr` is available:
```bash
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](references/installation.md) to install Alire.

Note: `alr` has comprehensive built-in help. At any point, `alr --help` lists all available subcommands and `alr
`<subcommand> --help` gives full usage details. Consult these whenever the reference files don't fully address the situation.

---

## Quick Reference Chart

| Alire Command | Description | Reference |
|---|---|---|
| — | Install Alire | [installation.md](references/installation.md) |
| `alr search` | Search for crates in the index | [alire-search.md](references/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](references/alire-toolchain.md) |  
| `alr get` | Fetch a crate from the index | [alire-get.md](references/alire-get.md) |
| `alr with` | Add a dependency | [alire-with.md](references/alire-with.md) |
| `alr pin` | Pin a dependency to a local path or Git repo | [alire-pin.md](references/alire-pin.md) |
| `alr install` | Install a binary-tool crate to a shared prefix | [alire-install.md](references/alire-install.md) |
| `alr build`  | Build the project | [alire-build.md](references/alire-build.md) |
| `alr run` | Run the project | [alire-run.md](references/alire-run.md) |
| `alr exec`  | Execute a command in the project environment | [alire-exec.md](references/alire-exec.md) |
| `alr printenv` | Print environment variables | [alire-printenv.md](references/alire-printenv.md) |
| — | Set up tests for a crate (AUnit, GNATtest) | [testing.md](references/testing.md) |
| — | Cross-compile for Raspberry Pi Pico | [raspberry-pi-pico.md](references/raspberry-pi-pico.md) |
| — | Cross-compile for Zephyr (Arm / RISC-V) | [zephyr.md](references/zephyr.md) |

   Commands Not in the Reference Chart

  If the user requests an alr workflow not covered above:

  1. Run `alr --help` to confirm the subcommand exists
  2. Run `alr <subcommand> --help` to read its full usage
  3. If the user asked a question, use the help output to answer it. If the user asked you to do something, execute the
  workflow derived from the help output.

From albertstarfield/eccAlbertport-ada, Apache-2.0.