From testdino
Use 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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/testdino:testdino-manual-runsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use TestDino manual-run tools when the user wants to manage a manual execution run or update case-level results inside a run.
Use TestDino manual-run tools when the user wants to manage a manual execution run or update case-level results inside a run.
Preferred flow:
health if projectId is not known.list_manual_runs to discover runs by name, state, release, environment, or tags.get_manual_run to inspect one run's metadata and rollup stats.create_manual_run or update_manual_run for run-level metadata changes.list_run_test_cases before changing any individual case in a run.update_run_test_case to assign a case, change its result, or update elapsed time.Important details:
runId accepts an internal ID or a counter-style ID like RUN-12.rtcRef can be the run test case row ID, case key like TC-156, or the underlying test case ID.updates.assigneeUserId can be a user ID or email address.updates.result accepts display form or canonical form, but canonical values like passed, failed, blocked, skipped, retest, and untested are safest.tags and linkedIssues must be JSON arrays.Good requests for this skill:
npx claudepluginhub testdino-hq/testdino-plugins --plugin testdinoProvides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.