onboard

Generate technical onboarding documentation from local repository source code.

2|Updated May 27, 2026
One-click install
npx skills add https://github.com/edlng/agents --skill onboard-edlng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/edlng/agents/tree/main/skills/universal/onboard
Command: npx skills add https://github.com/edlng/agents --skill onboard-edlng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the challenge of quickly understanding an unfamiliar codebase by automatically generating a comprehensive, evidence-based technical guide that covers architecture, runtime behavior, and operational risks.

Core Features & Use Cases

  • Evidence-Backed Analysis: Builds a technical map using verified repository data, git status, and project-native checks rather than relying on stale documentation.
  • Visual Architecture: Automatically generates icon-based architecture diagrams using diagrams.net or SVG fallbacks to visualize system boundaries and flows.
  • Use Case: A developer joins a new project and needs to understand the subsystem responsibilities, security boundaries, and major execution paths without manually tracing every file.

Quick Start

Use the onboard skill to generate a technical guide for the current repository and save it to the default Obsidian destination.

Frequently Asked Questions about onboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate technical onboarding documentation for an unfamiliar codebase?

Generate technical onboarding documentation by analyzing source code, configuration, and runtime behavior to map subsystem responsibilities and identify security boundaries. This process builds an evidence-based technical guide using verified repository data rather than relying on stale documentation.

What is the best way to automatically generate architecture diagrams from repository source code?

Automatically generate architecture diagrams from repository source code by analyzing system boundaries and execution flows. The process creates visual architecture using icon-based diagrams.net or SVG fallbacks to map subsystem responsibilities visually.

How does evidence-based codebase analysis identify security boundaries and operational risks?

Evidence-based codebase analysis identifies security boundaries and operational risks by running project-native checks and verifying git status against actual source code. This non-destructive verification method builds a technical map using verified repository data instead of outdated files.

Can I use automated repository analysis to map major execution paths without manually tracing files?

You can use automated repository analysis to map major execution paths without manually tracing every file. The analysis examines source code, configuration, and runtime behavior to generate a comprehensive technical guide covering subsystem responsibilities and architectural flows.

Does the generated technical guide support portable diagram formats for developer productivity workflows?

The generated technical guide supports portable diagram formats by outputting icon-based architecture diagrams using diagrams.net or SVG fallbacks. This satisfies developer productivity workflow requirements for rapid architectural understanding and portable diagram generation.

What are the limitations of using automated onboarding analysis for local software repositories?

Automated onboarding analysis for local software repositories focuses on non-destructive verification and portable diagram generation, limiting its scope to local repository environments. It relies on project-native checks and actual source code rather than integrating external runtime monitoring data.