agentsclimarketplace

Codebase onboarding

Skill DROOdotFOO/agent-skills/skills/codebase-onboarding

Agent skills, autonomous agents, and MCP-companions for programming

Install
npx -y skills add DROOdotFOO/agent-skills --skill codebase-onboarding

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Auto-generate onboarding documentation from codebase analysis, tailored to the reader's experience level. TRIGGER when: user asks to onboard someone to a codebase, document this codebase, generate project documentation for new team members, write a codebase walkthrough or tour, create a getting-started guide, or explain a codebase to a specific audience. DO NOT TRIGGER when: user wants API reference docs (use language-specific tooling), or wants to understand a single file (just read it).

SKILL.md

2.9 KB, as published. Nobody here has run it

codebase-onboarding

Auto-generate onboarding documentation from codebase analysis. Audience-aware output for junior developers, senior engineers, and contractors.

What You Get

  • Architecture overview derived from actual code structure
  • Key entry points and control flow
  • Testing strategy and deployment process
  • Domain glossary extracted from code and comments
  • Audience-tailored depth and focus

Workflow

  1. Analyze -- Scan the codebase to discover stack, structure, and patterns
  2. Capture signals -- Identify entry points, config files, CI/CD, test patterns, dependency graph, domain terms
  3. Fill template -- Populate the output format sections
  4. Tailor -- Adjust depth and emphasis for the target audience

Analysis signals

SignalWhere to look
Language/frameworkpackage.json, mix.exs, go.mod, Cargo.toml, pyproject.toml
Entry pointsmain files, router definitions, CLI entry points
Config.env.example, config/, settings files
CI/CD.github/workflows/, Makefile, Dockerfile
Teststest/, spec/, tests/, *_test.go
Databasemigrations/, schema files, ORM models
API surfaceOpenAPI specs, GraphQL schema, route definitions
Domain termsREADME, doc comments, module names, type names
DependenciesLock files, vendor/, package manifests
Dev setupMakefile, docker-compose.yml, devcontainer.json

Rules

  1. Derive everything from the actual codebase -- do not fabricate
  2. Flag gaps explicitly ("No CI/CD configuration found")
  3. Keep the glossary to terms a newcomer would not know
  4. Link to actual files using relative paths
  5. If the audience is not specified, ask before generating

Reference

FileTopic
audience-profiles.mdJunior/Senior/Contractor focus areas
output-template.mdMarkdown template for the onboarding doc

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.