Omm PushSAFE

Turn complex codebases into clear, navigable architecture diagrams with Claude Code.

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: omm-push
description: Push architecture docs to oh-my-mermaid cloud. Handles login, link, and push workflow with error guidance. Use when the user says "omm push", "push to cloud", "deploy architecture", or "share architecture".
---

# omm-push — Cloud Push Workflow

## Purpose

Automate the full workflow of pushing .omm/ architecture docs to the oh-my-mermaid cloud service.

## Prerequisites

Ensure the `omm` CLI is available:

```bash
command -v omm || npm install -g oh-my-mermaid
```

If the install command fails (permission denied), tell the user:
"Please run `npm install -g oh-my-mermaid` in your terminal, then try again."

## Workflow

### Step 1: Check Login Status

Run `omm share` via Bash. If it errors with "not logged in":
- Tell the user: "You need to log in first."
- Run `omm login` — this opens a browser for GitHub OAuth
- Wait for the user to complete login

### Step 2: Check Project Link

Run `omm share` via Bash. If it errors with "no project slug":
- Run `omm link` — this sets the cloud project slug from the directory name
- Confirm: "Linked to {slug}"

### Step 3: Push

Run `omm push` via Bash.

Handle errors:
- **401 Unauthorized**: "Login expired. Run `omm login` again."
- **403 Free plan limit**: "Free plan allows 1 project. Upgrade at https://ohmymermaid.com/pricing"
- **Network error**: "Cannot reach server. Check your connection."

### Step 4: Report

On success, output:
- Number of files uploaded
- View URL: `https://ohmymermaid.com/p/{slug}`
- Share URL (if Pro): "Run `omm share` to get the shareable link"

## Rules

- Always check login before pushing
- Always check link before pushing
- Do NOT skip steps — each depends on the previous
- If any step fails, stop and report the error with guidance

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.