π¦ ClawHub
Repo Onboarding
by @broedkrummen
Onboard a repo by assessing architecture and dependencies, setting up roadmap and kanban for execution, and generating a comprehensive onboarding report.
TERMINAL
clawhub install repo-onboardingπ About This Skill
name: repo-onboarding description: Onboard a coding repository with both technical architecture intake and execution governance. Use when starting in a new/existing repo and you need: (1) architecture snapshot + dependency analysis, (2) run/build/test bootstrap map, and (3) ROADMAP + feature KANBAN workflow setup for multi-agent execution.
Repo Onboarding
Combine senior-architect (technical intake) + repo-kanban-pm (execution governance).
Workflow
1. Technical intake (architecture + dependencies) 2. Execution system install (ROADMAP + KANBAN + bug inbox) 3. Onboarding report for handoff
Step 1 β Technical intake
Run from target repo root:
# 1) architecture assessment
python /home/broedkrummen/.openclaw/workspace-cody/skills/senior-architect/scripts/project_architect.py . --output json > docs/pm/architecture-assessment.json2) dependency analysis
python /home/broedkrummen/.openclaw/workspace-cody/skills/senior-architect/scripts/dependency_analyzer.py . --output json > docs/pm/dependency-analysis.json3) architecture diagram (mermaid)
python /home/broedkrummen/.openclaw/workspace-cody/skills/senior-architect/scripts/architecture_diagram_generator.py . --format mermaid -o docs/pm/architecture-diagram.md
If scripts fail, continue with manual fallback:
package.json, pyproject.toml, go.mod, etc.)docs/pm/ONBOARDING.mdStep 2 β Install execution governance
bash /home/broedkrummen/.openclaw/workspace-cody/skills/repo-kanban-pm/scripts/init_repo_pm.sh "$(pwd)"
Optional daily PM audit:
bash /home/broedkrummen/.openclaw/workspace-cody/skills/repo-kanban-pm/scripts/add_daily_pm_cron.sh "$(pwd)" --agent cody --tz UTC --time 09:30
Step 3 β Create onboarding report
Create docs/pm/ONBOARDING.md using references/onboarding-template.md.
Must include:
Exit criteria
Complete only when all are true:
docs/pm/architecture-assessment.json exists (or manual equivalent documented)docs/pm/dependency-analysis.json exists (or manual equivalent documented)docs/roadmap/ROADMAP.md existsdocs/features//KANBAN.md existsdocs/pm/ONBOARDING.md exists and is actionable