Module packages 

Preconfigured safety packages — named rule bundles for different workflows.

Packages are embedded TOML files that slot between stdlib and user config. They provide sensible defaults for common development scenarios so users can get started with a single package = "develop" setting.

Three built-in packages are available:

• review — full supervision, every command asks
• develop — auto-approves builds, tests, VCS; asks for destructive ops
• autopilot — maximum AI autonomy, only catastrophic ops blocked

Users may also define custom packages in ~/.rippy/packages/<name>.toml. Custom packages can extends = "<builtin>" to inherit from a built-in package and layer extra rules on top.

Structs

CustomPackage

A user-defined package loaded from ~/.rippy/packages/<name>.toml.

Enums

Package

A preconfigured safety profile.

Functions

discover_custom_packages

Scan ~/.rippy/packages/*.toml and return metadata-loaded custom packages.

load_custom_package

Load a single custom package by name from ~/.rippy/packages/<name>.toml.

package_directives

Parse a package’s TOML into config directives.

package_toml

Get the raw TOML source for a package.