# Omh Codebase Onboarding

[omh] Unfamiliar repository needing a guided tour: create a repo map, reading path...

- Repository: https://github.com/rlaope/oh-my-hermes (5004 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rlaope/oh-my-hermes --skill omh-codebase-onboarding -g -a claude-code -y`
Codex: `npx skills add rlaope/oh-my-hermes --skill omh-codebase-onboarding -g -a codex -y`
Cursor: `npx skills add rlaope/oh-my-hermes --skill omh-codebase-onboarding -g -a cursor -y`
Gemini CLI: `npx skills add rlaope/oh-my-hermes --skill omh-codebase-onboarding -g -a gemini-cli -y`

## Description

[omh] Unfamiliar repository needing a guided tour: create a repo map, reading path, glossary, risk map, and first-task runway for unfamiliar codebases. Use when the user says: codebase-onboarding, codebase onboarding, repo onboarding, repository onboarding, codebase tour, code tour, new repo orientation, understand this repo.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Codebase Onboarding

This is an OMH `codebase-onboarding` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

## Why This Exists

`codebase-onboarding` adapts ECC's code-tour and onboarding surfaces into an OMH-native first-read workflow so unfamiliar repos become navigable before implementation pressure starts.

## Do Not Use When

- The user already named a concrete implementation task and acceptance criteria; use `ulw-work` or `omh-idea-to-deploy`.
- The user needs a whole-workspace capability inventory; use `omh-workspace-audit`.
- The user wants a code diff review; use `omh-code-review`.

## Examples

Good example:

- Prompt: codebase-onboarding 처음 보는 레포라서 구조, 주요 모듈, 테스트, 첫 작업 후보를 잡아줘.
- Expected behavior: Prepare repo_map/v1, reading_path/v1, domain_glossary/v1, risk map, and first_task_runway/v1 from observed files.
- Why: The request is repo orientation before implementation.

Bad example:

- Prompt: codebase-onboarding 파일 안 읽고 이 레포 아키텍처를 확정해줘.
- Expected behavior: Mark architecture as unobserved and inspect source evidence before making claims.
- Why: Onboarding is only useful when grounded in current repo evidence.

## Completion Checklist

- The plan names goals, non-goals, assumptions, acceptance criteria, and verification shape.
- Draft recommendations, accepted decisions, and executor handoffs are separate states.
- Rejected options or unresolved tradeoffs are recorded before handoff.

## Recovery Notes

- If acceptance criteria or verification are missing, route back to clarification before handoff.
- If assumptions materially affect the plan, keep them visible and avoid treating the plan as accepted.



## When to Use

Use when Hermes should help an operator or coding executor understand an unfamiliar repository before planning implementation.

The rest: https://github.com/rlaope/oh-my-hermes/blob/HEAD/agent-skills/omh-codebase-onboarding/SKILL.md