devdocs-onboard

Scan repository and DevDocs to generate a context document at docs/devdocs/00-context.md.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ab300819/skills --skill devdocs-onboard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devdocs-onboard
Source: https://github.com/ab300819/skills/tree/main/devdocs-onboard
Command: npx skills add https://github.com/ab300819/skills --skill devdocs-onboard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate project context summaries for AI tool handover to simplify onboarding and tool switching.

Core Features & Use Cases

  • Scan DevDocs and repository to extract project overview, architecture, current progress, and pending tasks.
  • Produce a ready-to-share context document to accelerate onboarding of new AI tools or team members.
  • Supports intelligent detection of existing context and optional update mode to refresh the summary.

Quick Start

Run the onboarding tool to generate context: /devdocs-onboard Read existing context without modification: /devdocs-onboard --read Force a fresh scan and update: /devdocs-onboard --update

Frequently Asked Questions about devdocs-onboard

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

FAQPage Schema
How do I generate project context for AI handover when switching tools?

To generate project context for AI handover, use the onboarding tool to scan your repository and DevDocs. It extracts the project overview, architecture, and tasks, producing a ready-to-share context document for new AI sessions.

What is the best way to onboard a new team member using existing documentation?

The best way to onboard a new team member is to generate a self-contained project context summary. The tool scans your codebase and DevDocs to produce a document detailing current progress and pending tasks for quick integration.

How does codebase scanning work for creating AI context documents?

Codebase scanning for AI context documents works by reading the repository structure and DevDocs. It intelligently detects existing context, extracts architecture details, and writes a self-contained summary file at docs/devdocs/00-context.md.

Can I read existing project context without modifying the generated file?

Yes, you can read existing project context without modifying the generated file. Run the onboarding tool with the read option to safely view the current context summary without triggering a fresh codebase scan or update.

How do I force a fresh codebase scan and update the project context summary?

To force a fresh codebase scan and update the project context summary, run the onboarding tool with the update option. This bypasses existing context detection, rescans the repository, and refreshes the summary file with a new timestamp.