assura

AI coding agent guardrails

Guide the repair before a late gate forces it.

Hooks and CI are necessary, but they arrive after an agent has built on top of early drift. Assura adds bounded project signals during the working loop and reserves hard failure for configured merge policy.

Start with your agent Read agent-ready onboarding
assura review 
Assura reviewStatus     needs attentionScope      feature/agent-review -> origin/mainFindings   blocking=1 advisory=3 new=4Branch     feature/agent-review files=1 lines=+3/-0 commits=1Worktree   files=2 modified=1 untracked=1 lines=+2/-0Watch      blocking-validation=1/1Hot path   apps/web/src violations=1 changed=2 lines=+2/-0Fix first  apps/web/src/BadName.tsx: File 'BadName.tsx' does not match naming convention 'kebab-case'Next       Fix blocking configured check violations first.Run        assura check --format agent .

While editing

Return bounded advisory context in the agent loop without blocking the current change.

Before commit

Show branch, worktree, structure, and changed-path findings while the repair is still focused.

Before merge

Use the authoritative Check gate for serious configured policy that should not land.

01

Late gates distort repairs

When a commit is already blocked, the shortest path to green can become a broad refactor that breaks context and leaves technical debt.

02

Bound the feedback

Agent-facing output prioritizes a small number of repairable findings and points to deeper commands instead of dumping every observation.

03

Use branch and worktree context

Review separates committed branch changes from dirty worktree state so agents can see what this task introduced.

04

Keep human decisions visible

Onboarding reports inactive capabilities and unresolved project choices instead of pretending unchecked behavior passed.

Continue

Follow the signal into the details.

Agent setup

Set up this project with Assura.

Copy one instruction to the coding agent already working in your project. It will establish the baseline, define the expected shape, and verify it.

One command assura agent onboard .
Agent goal Inspect, constrain, verify
  1. Inspect manifests, tooling, generated output, and the intentional layout.
  2. Define project-owned rules for the expected stack. Close stable scopes so unexpected paths fail; preserve legitimate paths and ask only where evidence is ambiguous.
  3. Verify with assura review and assura check --format agent.
Installation details public release
curl -fsSL https://assura.dev/install.sh | sh

The copied setup instruction includes this command.