onboarding

Crawl a repository to generate ONBOARDING.md at the repo root.

50|14|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill onboarding-all-the-vibes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboarding
Source: https://github.com/All-The-Vibes/ATV-StarterKit/tree/main/.github/skills/onboarding
Command: npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill onboarding-all-the-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates or regenerates ONBOARDING.md to help new contributors understand a codebase. It crawls a repository to reconstruct the mental model from the code and writes a readable onboarding guide at the repository root.

Core Features & Use Cases

  • Rebuilds ONBOARDING.md from current code and docs
  • Documents project structure, setup steps, and contribution patterns
  • Produces a living reference that can be refreshed with each change

Quick Start

Generate ONBOARDING.md for the repository to help new contributors understand the codebase.

Frequently Asked Questions about onboarding

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

FAQPage Schema
How do I auto-generate onboarding documentation for a new codebase?

To generate onboarding guides, this skill crawls a repository to inventory key files and synthesizes a fresh ONBOARDING.md at the repo root for new contributors.

What is the best way to document project structure and setup steps for contributors?

Documenting project structure and setup steps is handled by reconstructing the mental model from code, writing a readable onboarding guide that details contribution patterns.

Can I regenerate an existing ONBOARDING.md file after code changes?

You can regenerate an existing ONBOARDING.md by running the tool again; it overwrites the current file at the repository root with a living reference refreshed from current code.

Does generating onboarding guides from a repository leak secrets or sensitive files?

Generating onboarding guides actively avoids leaking secrets; the tool orchestrates a deterministic inventory pass and reads key files to synthesize documentation without exposing sensitive data.

Do I need to manually write contributor guides when onboarding new developers?

Writing contributor guides manually is unnecessary; the tool automates inventory passes and file reading to produce a living reference documenting the codebase for new contributors.