Onboard

---
name: onboard
description: Connect an orchestrated repo to rossoctl/rossoctl as the hub - clone, configure, apply standards
---

```mermaid
flowchart TD
    START(["/onboard"]) --> ORCHESTRATED{Already orchestrated?}
    ORCHESTRATED -->|No| ORCH["Run orchestrate first"]:::prereq
    ORCH --> ORCHESTRATED
    ORCHESTRATED -->|Yes| LINK["onboard:link"]:::onb
    LINK --> STANDARDS["onboard:standards"]:::onb
    STANDARDS --> DONE([Connected to hub])

    classDef onb fill:#9C27B0,stroke:#333,color:white
    classDef prereq fill:#FF9800,stroke:#333,color:white
```

> Follow this diagram as the workflow.

# Onboard

Connect an orchestrated repository to rossoctl/rossoctl as the hub.

## Onboard vs Orchestrate

- **orchestrate** is generic — works on any repository to add CI, tests, skills.
  Does not assume the target is related to rossoctl.
- **onboard** is rossoctl-specific — clones the repo into `.repos/`, applies
  rossoctl conventions, and registers it in the hub inventory.

Run `orchestrate` first, then `onboard` to complete the connection.

## Prerequisites

Target repo must have completed at least:

1. `orchestrate:scan` — CLAUDE.md exists
2. `orchestrate:precommit` — pre-commit hooks installed

## Sub-Skills

| Skill | Description |
|-------|-------------|
| `onboard:link` | Clone into `.repos/`, verify skill discovery |
| `onboard:standards` | Apply rossoctl commit format, PR/issue templates |

## Workflow

1. Verify the target repo has been orchestrated
2. Run `onboard:link` — clone into `.repos/`, register in inventory
3. Run `onboard:standards` — apply rossoctl conventions via PR

## Related Skills

- `onboard:link` — Clone and register in hub
- `onboard:standards` — Apply rossoctl conventions
- `orchestrate` — Generic repo enhancement (prerequisite)