nanlabs/nanlabs-core
Recommended install: setup/onboarding, orchestrator, companion, handshake, Pyright report-only typing, PR fallback, knowledge sync, and code-reviewer agent
HOW — Default NaNLABS orchestrator. Use for repo discovery, conflict resolution, and routing to workflow/tool skills. Do NOT use for ticket CLI steps, forge automation, or deep procedure execution.
WHAT — NaNLABS Dev Companion (general): layered companion for client delivery; modes, gates, delegation to nanlabs-assistant and nanlabs-workflow-generic-project; no CLI matrices.
WHAT — Default gate for any deliverable: confirm where the final artifact will live and that a human will review, before writing PRDs, TRDs, ADRs, or PR bodies. Storage (repo, wiki, ticket) differs by engagement; never assume a single location.
WHAT, Structure the pull-request body with the NaNLABS default in references/pr-body-default.md when the repo has no GitHub PR template. Pair with nanlabs-output-handshake and github-cli-workflow. Does not open the PR; HOW stays in the forge skill.
HOW — Run Pyright in report-only mode for Python projects, summarize the diagnostics by severity and file, and recommend the next fix order without auto-applying code changes.
HOW — First-run setup for the NaNLABS agent toolkit. Inspect the local environment against bundled contracts, report missing baseline tools, ask approval before installs, and print a change report. Never print or store secrets.
Syncs knowledge to the internal-ai-workspace knowledge base. Use when the assistant discovers new patterns, learns user preferences, or identifies information worth preserving for future sessions. Can be triggered manually or by orchestrators.