One-click install
npx skills add https://github.com/wednesday-solutions/ai-agent-skills --skill onboard-dev-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard-dev-agent
Source: https://github.com/wednesday-solutions/ai-agent-skills/tree/main/skills/agents/onboard-dev
Command: npx skills add https://github.com/wednesday-solutions/ai-agent-skills --skill onboard-dev-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents new developers from getting lost, wasting time, or making junior-level mistakes by ensuring they understand the project using the repo’s actual structure and current graph coverage rather than assumptions.

Core Features & Use Cases

  • Graph gap filling before answers: Detects high-risk areas with low graph coverage and fills missing graph data to make onboarding reliable, not speculative.
  • Guided, graph-cited onboarding interview: Runs a structured sequence of questions (what it does, main modules, risks, recent changes, rules to not break, and test coverage) and expects answers backed by sources in the repo graph and artifacts.
  • Change-aware navigation for quick ramp-up: Uses blast/risk-relevant signals from dependency graph and git history so the newcomer can safely choose what to explore first.

Quick Start

Ask: “Onboard me to this codebase, fill any low-coverage graph gaps first, then run the guided overview interview and tell me where to start.”

Frequently Asked Questions about onboard-dev-agent

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

FAQPage Schema
How do I onboard new developers to a brownfield codebase quickly?

Developer onboarding for brownfield repositories is accelerated by generating a graph-backed project overview, module map, and risk analysis to orient newcomers in minutes using actual repo structure.

What is the best way to identify risk areas and non-breaking architecture rules in an unfamiliar project?

Identifying risk areas and architecture rules involves analyzing the dependency graph and git history, which highlights high-risk modules and test coverage gaps to guide safe codebase exploration.

How do I generate a codebase orientation guide that cites actual source files?

Codebase orientation guides are generated through a structured interview that answers project overview questions while citing sources directly from the repository graph artifacts.

Does developer onboarding work reliably when the dependency graph has low coverage?

Developer onboarding remains reliable because the tool first runs gap-filling to detect high-risk areas with low graph coverage, ensuring the orientation is based on complete data rather than assumptions.

When do I need to fill graph gaps before navigating an unfamiliar codebase?

Filling graph gaps is needed before navigating an unfamiliar codebase when high-risk areas have low coverage, preventing speculative onboarding and ensuring new developers understand the project reliably.

Can I use git history and dependency graphs to guide new developer codebase exploration?

Git history and dependency graphs are used to generate blast and risk-relevant signals, allowing new developers to safely choose which recent changes and modules to explore first during onboarding.