test-publish

Publish a test-readiness plan as labeled GitHub issues with a tracking issue.

9|2|Updated Jun 6, 2026

Search Tags:#github #milestones #issues #labels #cli-automation #test-readiness

Ready to run

npx skills add https://github.com/app-vitals/shipwright --skill test-publish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-publish
Source: https://github.com/app-vitals/shipwright/tree/main/plugins/shipwright/skills/test-publish
Command: npx skills add https://github.com/app-vitals/shipwright --skill test-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a static test-readiness plan into a live GitHub issue dashboard so teams can track implementation work, dependencies, and review status without manually copying tasks into issues.

Core Features & Use Cases

Plan publication: Reads the approved test-readiness roadmap and creates one GitHub issue per task.
Workflow orchestration: Adds milestones, labels, dependency-aware ready or blocked states, and a parent tracking issue.
Idempotent publishing: Detects existing published tasks so reruns do not duplicate issues.
Operational use case: Use it when a repository needs a searchable, self-contained backlog for test implementation that developers can pick up directly from GitHub.

Quick Start

Use the test-publish skill to publish the approved test-readiness plan into labeled GitHub issues and a tracking issue after confirming the target repository scope.

Frequently Asked Questions about test-publish

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

FAQPage Schema

How do I publish a test-readiness plan into GitHub issues?▼

To publish a test-readiness plan into GitHub issues, you use a skill that reads the approved roadmap and automatically generates one issue per task, complete with milestones and dependency-aware labels. This creates a live tracking dashboard directly in your repository.

Does publishing GitHub issues from a test plan duplicate tasks on reruns?▼

Publishing GitHub issues from a test plan does not duplicate tasks on reruns because the process uses idempotent publishing with built-in deduplication markers. It detects existing published tasks to ensure the backlog remains clean and current.

How do I add milestones and dependency-aware labels to GitHub issues automatically?▼

You can add milestones and dependency-aware ready or blocked labels to GitHub issues automatically by orchestrating the workflow through CLI automation. This applies the required labels and creates milestones based on the source plan's structure.

Do I need GitHub CLI authentication to generate a tracking issue dashboard?▼

Yes, you need GitHub CLI authentication to generate a tracking issue dashboard. The process requires CLI access to create the parent tracking issue, generate task-specific issues, and apply labels and milestones within the target repository scope.

What is a parent tracking issue for test implementation backlogs?▼

A parent tracking issue for test implementation backlogs is a single, always-current GitHub issue that links to all generated task issues. It provides a searchable, self-contained dashboard so developers can monitor dependency-aware readiness and review status.

Can I use this test plan publication method for repository test-planning workflows?▼

Yes, you can use this publication method for repository test-planning workflows that need milestone-based issue generation. It is designed to turn static roadmaps into a live backlog with immutable context links to the source plan.