codebase-onboarding
/codebase-onboarding
Onboard a developer to a repository using Ontoly graph summaries. Use when asked to explain a new codebase, identify entrypoints, map packages, or suggest first files to inspect.
- Author
- sickn33 ↗
- Repository
- agentic-awesome-skills ↗
- Licence
- MIT
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 10
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 4
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Onboard a developer to a repository using Ontoly graph summaries. Use when asked to explain a new codebase, identify entrypoints, map packages, or suggest first files to inspect.
Original author description
Onboard a developer to a repository using Ontoly graph summaries. Use when asked to explain a new codebase, identify entrypoints, map packages, or suggest first files to inspect.
How it works
- When to Use
- Required Workflow
- Ontoly Capabilities
- Output Contract
- Boundaries
- Resources
- Learn more
- Examples
- Limitations
SKILL.md preview
---
name: codebase-onboarding
description: Onboard a developer to a repository using Ontoly graph summaries. Use
when asked to explain a new codebase, identify entrypoints, map packages, or suggest
first files to inspect.
license: AGPL-3.0-only
compatibility: Portable Agent Skills format; requires Ontoly CLI and MCP-capable or
CLI-capable coding agent.
metadata:
ontoly.skill.version: 1.3.3
ontoly.min.version: 1.3.3
ontoly.capabilities: ExplainArchitecture, FindEntrypoints, GraphStatistics, FindFeatureOwner,
EvidencePack
ontoly.category: onboarding
ontoly.enhancement: LLM Enhancement
ontoly.deprecated: 'false'
source_repo: 0xsarwagya/ontoly
source_type: community
source: community
date_added: '2026-09-21'
risk: unknown
---
## When to Use
- Use when this upstream workflow matches the user's stated goal.
- Use when the task requires the procedures documented in this skill.
# Codebase Onboarding
Use this skill when the user asks for codebase onboarding using Ontoly evidence.
## Required Workflow
Follow [the shared Ontoly workflow](reference/workflow.md), [graph evidence rules](reference/graph.md), [MCP usage](reference/mcp.md), [best practices](reference/best-practices.md), and [fallback rules](reference/fallbacks.md). Frontmatter version requirements supersede older 1.0.0 labels in companion notes; verify installed capabilities before use.
## Ontoly Capabilities
Use these capabilities first: `ExplainArchitecture`, `FindEntrypoints`, `GraphStatistics`, `FindFeatureOwner`, `EvidencePack`.
## Output Contract
Return:
- answer or plan
- capabilities invoked
- graph evidence with node ids, edge types, source spans, and graph hash when available
- confidence: high, medium, or low
- fallback reason if repository files were inspected
## Boundaries
Do not implement compiler, query, MCP, SDK, or business logic in the skill. Do not search repository files until Ontoly cannot answer or evidence must be confirmed.
## Resources
- [Examples](examples.md)
- [Prompt template](templates/repository-onboarding.md)
- [Capability notes](reference/capabilities.md)
## Learn more
- Documentation: https://ontoly.xyz/docs
- This skill on the web: https://ontoly.xyz/skills#codebase-onboarding
- All Ontoly Agent Skills: https://ontoly.xyz/skills
- Install via skills.sh: https://www.skills.sh/?q=0xsarwagya/ontoly
## Examples
```text
User: Apply this skill to my current task.
Assistant: Follow the workflow in this skill, cite limitations, and ask before risky steps.
```
## Limitations
- Imported upstream skill; verify credentials, permissions, and safety boundaries before execution.
- Does not replace environment-specific validation, testing, or maintainer review.
Files in this package (10)
- README.md 1 KB
- SKILL.md 3 KB
- examples.md 3 KB
- reference/best-practices.md 1 KB
- reference/capabilities.md 1 KB
- reference/fallbacks.md 1 KB
- reference/graph.md 1 KB
- reference/mcp.md 1 KB
- reference/workflow.md 1 KB
- templates/repository-onboarding.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · sickn33/agentic-awesome-skills | 100 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| FrancoStino/opencode-skills-collection | 100 | MIT |
| neuromechanist/research-skills | 100 | BSD-3-Clause |
| alirezarezvani/claude-skills | 100 | MIT |
| kannnnna9/ultracode | 100 | MIT |
| reddygopalkrishna/developer-agent-skills | 100 | MIT |
| SHRIJANAGAIN/Nemo-Cli | 100 | Apache-2.0 |
| ssvinar/senior-agent-skills | 100 | MIT |
Identical content appears in 2 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version bdd34b7d1265 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100documentation
Draft graph-backed documentation from Ontoly summaries and traces. Use when asked to document architecture, APIs, modules, packages, or request lifecycles without re-parsing source files. - 90repo-onboarding
Use when starting in an unfamiliar repository, new codebase, greenfield checkout, or 'where do I start' moment and you need a fast structured map of stack, entrypoints, patterns, risks, and next steps before any edits. Triggers: onboard me to this repo, map the codebase, explore unfamiliar project. - 100dependency-analysis
Analyze internal and package dependencies using Ontoly graph traversal. Use when asked which modules, packages, services, or files depend on each other. - 100dependency-analysis
Analyze internal and package dependencies using Ontoly graph traversal. Use when asked which modules, packages, services, or files depend on each other. - 100dependency-analysis
Analyze internal and package dependencies using Ontoly graph traversal. Use when asked which modules, packages, services, or files depend on each other. - 100onboard-codebase
Map an unfamiliar repository from the files actually read (what it is, entry points, how to run and test it, conventions, risks) and propose lines for the project memory. Use it when starting in a project new to you, when asked to explain or map a codebase, or while its memory is empty.