testdino-runs
Use 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 Test Runs
Use TestDino tools when the user wants to inspect automated test results.
Preferred flow:
- Call
healthifprojectIdis not known. - Use
list_testrunsto find the relevant run. - Use
get_run_detailsfor one specific run. - Use
list_testcaseorget_testcase_detailsfor deeper failure analysis. - Use
debug_testcasewhen the user wants historical debugging context for a failing test.
Good requests for this skill:
- show failed runs on a branch
- inspect flaky tests
- summarize one test run
- debug a failing testcase with history
Common filters from the docs:
- branch
- time interval
- author
- commit
- environment
- status
- browser
- error category
- tags
Use list_testruns first when the user does not already know the exact run ID or counter.
Use debug_testcase when the user wants root-cause analysis and recommendations across historical runs, not just a single-run snapshot.
Use health at the start of a session when the project is still ambiguous.
anthropics/claude-plugins-community · MIT · Revision a727be1c7bd6
Be the first to comment
Share what worked or leave a question for the creator.