td-feature-integrate

Coordinate tdmcp tool changes into shared registries, CLI, and docs.

30|6|Updated May 25, 2026

Search Tags:#documentation #cli #tooling #registry #tdmcp #concurrent-editing

Ready to run

npx skills add https://github.com/Pantani/tdmcp --skill td-feature-integrate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: td-feature-integrate
Source: https://github.com/Pantani/tdmcp/tree/main/.agents/skills/td-feature-integrate
Command: npx skills add https://github.com/Pantani/tdmcp --skill td-feature-integrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate concurrent edits to shared tdmcp artifacts — registries, CLI, and docs — in a conflict-safe, additive manner so parallel tool work can converge cleanly into a green typecheck + build.

Core Features & Use Cases

Register tools by updating the appropriate layer registries and ensuring the central index aggregates changes without duplication.
Wire the CLI command mapping to each tool’s handler and keep the CLI surface in sync with the registry.
Regenerate and validate docs automatically from the live registry after integration, avoiding manual hand edits.
Enforce additive edits and provide guidance for resolving conflicts when two builders touch the same files.

Quick Start

Begin by validating the workspace state, then register a tool by updating the registries, CLI, and docs, regenerate documentation, and confirm a green typecheck + build.

Frequently Asked Questions about td-feature-integrate

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

FAQPage Schema

How do I integrate new tools into a shared registry without causing conflicts during parallel development?▼

To integrate tools safely during parallel development, update layer registries and CLI mappings additively, regenerate docs via scripts, and validate with typecheck and build to ensure a green state before QA restarts.

What is the best way to keep CLI command mappings in sync with a tool registry?▼

Keeping CLI command mappings in sync requires wiring each tool's handler to the CLI surface in src/cli while updating the central index in src/tools, ensuring the registry aggregates changes without duplication.

How do I automate documentation regeneration after adding new tools to a registry?▼

Automate documentation regeneration by running scripts that extract the live registry state and validate the output, avoiding manual hand edits and ensuring docs reflect the latest integrated tools.

Does additive editing prevent conflicts when multiple builders update the same CLI and registry files?▼

Additive editing prevents conflicts by enforcing non-destructive updates to shared artifacts, providing guidance to resolve overlaps when two builders touch the same files during concurrent tool development.

What steps are needed to validate a workspace before wiring new tools into shared registries?▼

Validating a workspace before wiring tools involves checking the current state, then registering the tool by updating registries, CLI, and docs, followed by confirming a green typecheck and build.

Why does typecheck fail after manually editing registry files instead of using an additive integration process?▼

Typecheck fails after manual edits because the central index may not aggregate changes correctly, causing duplication or missing CLI mappings, whereas additive integration enforces structural consistency across artifacts.