superclaw-onboard

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.

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.

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.

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.

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.

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.