[omh] Hermes Codebase Onboarding workflow: create a repo map, reading path, glossary, risk map, and first-task runway for unfamiliar codebases.
SkillScore75Maintained
Automatic
◆Coding pack
Last verified 8/27/2026
What it changes
Passed 14 of 18 test cases with the skill, and 6 of 18 without it.
Without skill33%
With skill75%
Checks it passed that the model alone missed
The response routes the request to workspace-audit.
The response explicitly defines the stop condition.
The response enforces a read-only boundary during onboarding.
and 12 more in the full report
11 fixed7 passed either way5 still failing1 broke
Pass-rate lift
+42 pp
Tokens
+92%
Agent turns
0%
Response time
0%
Model gemini-3.6-flashMeasured 8/27/2026v318 of 24 cases passed with skill · 18 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
I have a specific bug fix in `src/auth/jwt.py`: token expiration check throws `TypeError` when `exp` is missing in payload. Here are the acceptance criteria: return 401 response and log warning. Modify `jwt.py` now.
What was checked, without and with the skill
Checked
Without skill
With skill
The response routes the request to an implementation workflow like ultrawork.
Missed
Passed
case-04 · gemini-3.6-flash · 8/27/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md121 linessingle file
Codebase Onboarding
This is a Hermes-native codebase-onboarding workflow skill.
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 ultrawork or idea-to-deploy.
The user needs a whole-workspace capability inventory; use workspace-audit.
The user wants a code diff review; use 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.