superclaw-onboard

Name: superclaw-onboard
Availability: InStock
Author: liuzeming

Generate a centralized project context document from repository metadata and config files.

9|Updated Mar 28, 2026

Search Tags:#automation #software-engineering #project-context #onboard #context-generation #repository-scan #workflow-bootstrapping

Ready to run

npx skills add https://github.com/liuzeming-yuxi/SuperClaw --skill superclaw-onboard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: superclaw-onboard
Source: https://github.com/liuzeming-yuxi/SuperClaw/tree/main/skills/onboard
Command: npx skills add https://github.com/liuzeming-yuxi/SuperClaw --skill superclaw-onboard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Onboard phase automates the initial gathering of project context for SuperClaw, eliminating manual, error-prone context collection and ensuring subsequent phases start from a consistent foundation.

Core Features & Use Cases

Auto-scan repository to generate .superclaw/context/project-context.md.
Extract key project details from common config files (package.json, Cargo.toml, go.mod, pyproject.toml) and summarize top-level structure.
Capture recent activity from git logs and top-level directory structure for quick reference.
Produce Architecture Notes from README.md and CLAUDE.md if available.

Quick Start

Trigger onboarding to scan the project and generate .superclaw/context/project-context.md.

Frequently Asked Questions about superclaw-onboard

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

FAQPage Schema

How do I automate project context generation for repository onboarding?▼

Automating project context generation involves scanning repository metadata and common config files to produce a centralized context document. This skill reads files like package.json or go.mod, extracts project details, and outputs a concise context file for seamless onboarding.

What project details are extracted during a repository scan for onboarding?▼

A repository scan extracts the project name, language, framework, package manager, and recent activity. It reads common config files like pyproject.toml and Cargo.toml, captures git log activity, and summarizes the top-level directory structure into a context file.

Can I generate a project context document without modifying source code or installing dependencies?▼

Yes, you can generate a project context document without modifying source code or installing dependencies. This scanning process strictly reads existing files like README.md and config files, then outputs the context without altering your project environment.

Does workflow bootstrapping support projects using multiple package managers like Cargo and npm?▼

Workflow bootstrapping supports projects using multiple package managers by reading common config files including Cargo.toml, package.json, go.mod, and pyproject.toml. It identifies the specific package manager and language to summarize them accurately in the context document.

What is the best way to capture recent git activity for architecture notes?▼

Capturing recent git activity for architecture notes is done by scanning git logs during the repository onboarding process. The skill summarizes this recent activity alongside top-level directory structures and README.md content to provide quick reference context.

Where is the generated project context file stored after a repository scan?▼

The generated project context file is stored at .superclaw/context/project-context.md. This centralized location ensures subsequent workflow phases can consistently access the extracted project metadata and architecture notes without needing a re-scan.