understand-onboard

Generates a new-team-member onboarding guide from a project knowledge graph JSON.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill understand-onboard-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: understand-onboard
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/understand-onboard
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill understand-onboard-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New developers joining a project often spend days reading code to understand architecture, key files, and risky areas. This Skill turns an existing knowledge graph into a structured onboarding guide so newcomers get a curated learning path instead of raw exploration. ## Core Features & Use Cases - Graph-driven guide generation: Reads project metadata, architecture layers, guided tour steps, and file-level nodes from knowledge-graph.json to build a complete onboarding document. - Freshness validation: Compares the graph's recorded git commit against the current HEAD and project-scoped diffs, warning when the graph may be stale before generating content. - Complexity hotspot detection: Surfaces the highest-complexity files so new developers know which areas to approach carefully. - Use Case: A new engineer joins a monorepo team. Run this Skill to produce a markdown guide with project overview, architecture layers, a guided tour, a file map, and complexity hotspots, then save it to docs/UA_ONBOARDING.md and commit it for the whole team. ## Quick Start Ask the assistant to generate an onboarding guide for new team members from the project's knowledge graph.

Frequently Asked Questions about understand-onboard

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

FAQPage Schema
How do I generate an onboarding guide for new developers on a project?

Run this Skill after building the project's knowledge graph with the /understand command. It reads the graph's layers, tour, and file-level nodes, then produces a markdown guide with overview, architecture, file map, and complexity hotspots.

What is a knowledge graph JSON for codebase documentation?

It is a JSON file describing a project with typed nodes (files, functions, configs, services), edges (imports, calls, depends_on), architecture layers, and a guided tour. This Skill consumes that structure to assemble onboarding content without re-reading the source code.

Does the onboarding guide stay accurate after code changes?

The Skill checks the graph's recorded git commit against the current HEAD and project-scoped diffs before generating. If project files changed since the graph was built, it warns you and suggests rerunning /understand to refresh the graph.

What happens if the knowledge graph file is missing?

The Skill checks for knowledge-graph.json in the .ua or legacy .understand-anything directory first. If it does not exist, it tells you to run /understand first instead of attempting to generate a guide.

Where is the generated onboarding guide saved?

After generating the markdown, the Skill offers to save it to docs/UA_ONBOARDING.md in the project and suggests committing it to the repository so the whole team can use it.