dev-guide-contributing

Guides LingTai contribution workflows covering issues, worktrees, PRs, daemons, and anatomy maintenance.

692|60|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Lingtai-AI/lingtai --skill dev-guide-contributing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-guide-contributing
Source: https://github.com/Lingtai-AI/lingtai/tree/main/tui/internal/preset/skills/lingtai-dev-guide/reference/contributing
Command: npx skills add https://github.com/Lingtai-AI/lingtai --skill dev-guide-contributing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Contributing to the LingTai ecosystem spans multiple repos (TUI, portal, kernel, MCP addons) with strict conventions around worktrees, daemon orchestration, i18n locales, and anatomy citations; this reference encodes those rules so contributors follow the correct workflow instead of guessing.

Core Features & Use Cases

  • Issue-to-merge workflow: Enforces the issue → worktree/branch → PR → merge loop with exact-object approval gates before any worktree cleanup.
  • Daemon orchestration discipline: Defines how orchestrators decompose work into scoped briefs for Claude Code and Codex daemons with disjoint worktrees and validation steps.
  • Repo-specific build/test commands: Documents make, go test, pytest, and editable-install commands for the TUI, portal, kernel, and MCP addons, plus the three-locale i18n rule and anatomy citation maintenance.
  • Use Case: Before dispatching a daemon to fix a TUI screen bug, consult this guide to create the issue, spin up an isolated worktree, write a scoped brief with a do-not-touch list, and update the affected ANATOMY.md in the same commit.

Quick Start

Read this contributing reference before starting any non-trivial LingTai change and follow its issue, worktree, daemon dispatch, and PR workflow for your target repo.

Frequently Asked Questions about dev-guide-contributing

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

FAQPage Schema
How do I contribute code to the LingTai project?

Open or pick a GitHub issue, create an isolated git worktree on a topic branch off origin/main, make the change, then open a PR citing the issue. Non-trivial work should be dispatched to daemon backends with scoped briefs rather than hand-coded by the orchestrator.

How do I build and test the LingTai TUI?

Run make build in the tui directory to produce tui/bin/lingtai-tui, and go test ./... to run the test suite. The binary is named lingtai-tui, never lingtai, which is the separate Python agent CLI.

When is it safe to remove a git worktree?

Only after a read-only inventory shows it merged, clean, and unreferenced, and the human approves the exact worktree path and branch. An audit establishes eligibility but never authorizes deletion, and force removal or pruning requires explicit per-object approval.

Do LingTai project migrations still run in production?

No. The tui/internal/migrate and portal/internal/migrate registries are retained only for history and tests. Live migrations exist only in tui/internal/globalmigrate under ~/.lingtai-tui, run at TUI startup.

What must accompany a code change that moves cited files?

Any change that moves, renames, splits, merges, or deletes something cited by an ANATOMY.md must update that anatomy file in the same commit. Citations use file:line references verified against the actual code.