domains / families / software-engineering / codebase-onboarding

codebase-onboarding

combined

Codebase Onboarding Onboard a developer to a repository using Ontoly graph summaries. Use

When to use

• Onboarding a new team member or contractor
• After a major refactor that made existing docs stale
• Before open-sourcing a project
• Creating a team wiki page for a service
• Self-documenting before a long vacation
• Use when this upstream workflow matches the user's stated goal.
• Use when the task requires the procedures documented in this skill.

When not to use

• Imported upstream skill; verify credentials, permissions, and safety boundaries before execution.
• Does not replace environment-specific validation, testing, or maintainer review.

Skill page

Conflict

The two skills define fundamentally different procedures for onboarding to a codebase. The first skill (sickn33) is a wrapper for a specific external tool (Ontoly) and relies on graph-based evidence, MCP capabilities, and a specific output contract involving node IDs and graph hashes. It explicitly forbids searching repository files until the tool fails. The second skill (LeoYeAI) is a manual, shell-based analysis workflow that uses standard Unix commands (find, grep, git log) to gather facts and then generates comprehensive Markdown documentation (README, architecture diagrams, setup guides). They do not overlap in their core methodology; one is tool-dependent and abstract, the other is command-driven and concrete. Combining them is necessary to capture both the tool-based graph approach and the manual shell-based documentation approach.