Publish a test-readiness plan as labeled GitHub issues with a tracking issue.
npx skills add https://github.com/app-vitals/shipwright --skill test-publish
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
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.
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.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
dapperdiversManage GitHub project roadmaps by creating and tracking issues, milestones, and pull requests.
walker-hzxTrack and log task execution status with timestamps and issue details.
luokai25Develop test automation frameworks, scripts, and CI/CD pipeline integrations.
intraleManage GitHub issue backlogs with labels and Project V2 statuses.
