testdino-releases

$npx mdskill add anthropics/claude-plugins-community/testdino-releases

List, inspect, create, and update releases in TestDino projects

  • Identify project health to ensure it's ready for release operations.
  • Use `list_releases`, `get_release`, `create_release`, or `update_release` as needed.
  • Decide based on user needs: discovery, full details, changes, or creation.
  • Return results directly to the user in a clear and actionable format.

SKILL.md

.github/skills/testdino-releasesView on GitHub ↗
---
name: testdino-releases
description: Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers list_releases, get_release, create_release, and update_release. Accepts counter-style IDs like MS-12.
---

# TestDino Releases

Use TestDino release tools when the user wants to browse, inspect, create, or update releases in a project.

Preferred flow:

1. Call `health` if `projectId` is not known.
2. Use `list_releases` when the user needs discovery, filtering, or release lookup.
3. Use `get_release` when the user already has a specific `releaseId` or needs full release details.
4. Use `create_release` or `update_release` for release changes.

Important details:

- `releaseId` accepts either the internal ID or a counter-style ID like `MS-12`.
- `type` accepts either display form or canonical form, but canonical lowercase values are safest.
- `linkedIssues` must be sent as a JSON array for create and update operations.

Good requests for this skill:

- list releases in a project
- show details for release MS-12
- create a sprint or iteration release
- update release dates or status

More from anthropics/claude-plugins-community

SkillDescription
eli5Explain a topic like I'm a 5 year old. Use when the user types /eli5 <topic> or asks for a dead-simple picture explainer of how something works.
html-planWrite an implementation plan as one interactive HTML page - a tree of claims (why › what › how › where), each proved by one exhibit (UI mockup, state machine, call stack, schema or code), with the decisions the user has to make placed on the claim they change. Use when the user types /html-plan, or asks for a plan, RFC or design before building something that touches more than a couple of files.
quickdesignUse the `quickdesign` CLI to generate AI media — UGC promo videos, image edits, product creatives, video upscales — through Seedance, Kling, Sora2, Nano Banana, and GPT Image. Invoke this skill whenever the user asks for a talking-avatar video, multi-segment ad / promo / explainer, image edit (object swap, angle change, state change), product photoshoot, or video upscale via QuickDesign.
testdino-auditUse only when the user explicitly asks for a TestDino audit of Playwright automated test code. Routes through the audit tools the TestDino MCP server exposes (get_audit_report + submit_audit_report, or the legacy test_audit). For generic code review or non-Playwright targets, do a normal review instead.
testdino-healthUse when the user wants to check TestDino connection status, validate their PAT, discover available organizations and projects, or find the right projectId. Always call this first when the project context is ambiguous before any other TestDino tool.
testdino-manual-runsUse when the user wants to manage a manual execution run or update case-level results inside a run — listing runs, creating runs for a release, inspecting a run, assigning cases, or marking case results (passed/failed/blocked/skipped/retest/untested). Accepts counter-style IDs like RUN-12 and TC-156.
testdino-manual-testsUse when the user wants to create, update, or browse manual QA test cases and suites in TestDino — not execution runs. Covers list_manual_test_suites, list_manual_test_cases, get_manual_test_case, create_manual_test_case, update_manual_test_case, create_manual_test_suite.
testdino-runsUse when the user wants to inspect automated test runs, list failed or flaky tests, debug a failing testcase with historical context, or filter runs by branch, commit, author, environment, browser, status, or tags. Includes list_testruns, get_run_details, list_testcase, get_testcase_details, and debug_testcase.
testdino-sessionsUse when the user wants to browse, inspect, create, or update exploratory testing sessions in TestDino — by state, status, session type, assignee, release, or tags. Covers list_sessions, get_session, create_session, and update_session. Accepts counter-style IDs like SES-12.
tres-asc845-swap-reprice-skill>