engineering-team/playwright-pro/skills/testrail/SKILL.md
Sync tests with TestRail. Use when user mentions "testrail", "test management", "test cases", "test run", "sync test cases", "push results to testrail", or "import from testrail".
npx skillsauth add alirezarezvani/claude-skills testrailInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Bidirectional sync between Playwright tests and TestRail test management.
Environment variables must be set:
TESTRAIL_URL — e.g., https://your-instance.testrail.ioTESTRAIL_USER — your emailTESTRAIL_API_KEY — API key from TestRailIf not set, inform the user how to configure them and stop.
/pw:testrail import --project <id> --suite <id>
Steps:
testrail_get_cases MCP tool to fetch test casestest.info().annotations.push({ type: 'testrail', description: 'C12345' })/pw:testrail push --run <id>
Steps:
npx playwright test --reporter=json > test-results.json
testrail_add_result MCP tool for each test:
/pw:testrail run --project <id> --name "Sprint 42 Regression"
Steps:
testrail_add_run MCP tool/pw:testrail status --project <id>
Steps:
TestRail cases: 150
Playwright tests with TestRail IDs: 120
Unlinked TestRail cases: 30
Playwright tests without TestRail IDs: 15
/pw:testrail update --case <id>
Steps:
testrail_update_case MCP tool to update steps| Tool | When |
|---|---|
| testrail_get_projects | List available projects |
| testrail_get_suites | List suites in project |
| testrail_get_cases | Read test cases |
| testrail_add_case | Create new test case |
| testrail_update_case | Update existing case |
| testrail_add_run | Create test run |
| testrail_add_result | Push individual result |
| testrail_get_results | Read historical results |
All Playwright tests linked to TestRail include:
test('should login successfully', async ({ page }) => {
test.info().annotations.push({
type: 'testrail',
description: 'C12345',
});
// ... test code
});
This annotation is the bridge between Playwright and TestRail.
development
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
development
Use when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into owned action items — or says "should this be a meeting", "/cs:meeting-prep", or "/cs:meeting-actions". Runs a cost gate (ASYNC / NOT-READY / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist that flags every orphan.
development
Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.
development
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.