testspec-publish

Publish approved tests from a change workspace to testlib with routing and deduplication.

5|1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/winhok/testkit --skill testspec-publish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testspec-publish
Source: https://github.com/winhok/testkit/tree/main/skills/testspec-publish
Command: npx skills add https://github.com/winhok/testkit --skill testspec-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TestSpec 用例入库流程复杂,需要在变更工作区与知识库之间进行分类、合并、以及变更日志管理。本技能将自动化完成这一步骤,确保用例在 testlib 中有序沉淀并可追溯。

Core Features & Use Cases

  • Automatic routing: route test cases to the correct module/feature using naming dictionaries when available.
  • Incremental merge and de-dup: update existing cases by ID, add new cases, and preserve history.
  • Cross-reference and indexing: automatically update related_features and rebuild global index, with changelog generation.

Quick Start

Publish approved tests from testspec/changes to testlib, performing routing, dedup, and changelog updates.

Frequently Asked Questions about testspec-publish

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

FAQPage Schema
How do I publish approved tests to a testlib knowledge base?

To publish approved tests to a testlib knowledge base, this skill automates the workflow by applying routing, deduplication, and changelog generation directly from your change workspace.

How does test case routing work when merging into module files?

Test case routing uses a naming dictionary for precise module file merging, but automatically falls back to degraded routing to continue the publish workflow when the dictionary is missing.

What is the best way to deduplicate test cases during an incremental merge?

Deduplicating test cases during an incremental merge is handled by updating existing cases by ID, adding new cases, and preserving history to ensure no duplicate entries persist in the testlib.

How are changelogs and indexes updated when publishing test specifications?

Publishing test specifications updates changelogs and indexes by automatically updating related_features, rebuilding the global index, and generating logs for full traceability.

Can I publish tests if the naming dictionary for routing is missing?

Yes, you can publish tests when the naming dictionary is missing because the skill validates inputs and falls back to degraded routing to ensure the publish workflow completes successfully.

Why does publishing test specifications require validation and rebuild steps?

Publishing test specifications requires validation and rebuild steps to ensure accurate data merging into module files, rebuild the global index correctly, and maintain reliable logs for traceability.