agentleFS
MohamedRamadanSalahMohamedRamadanSalah/claude-qa-toolkit/.claude/skills/automate/SKILL.md

automate

Skill0 starsChanged 17 days agoMITView on GitHub

Convert manual test cases into automated tests (Playwright for UI, pytest/requests for API) and help build or extend a test automation framework. Use when the user wants to automate test cases, write Playwright/Selenium scripts, or set up test automation.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review-bugbot, origin and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • 0mlkrizzz655335vSkill

    review-bugbot

    缺陷导向代码审查。用 Bugbot 子代理找 bug。

    Also in 4 projects that use this

  • 0mlkrizzz655335vSkill

    origin

    origin CLI 管理。安装、登录、更新、修复 origin.cursor.com 的 CLI。"disabled-environments:

    Also in 3 projects that use this

  • PandelisZSkill

    update-cli-config

    View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.

    Also in 4 projects that use this

  • 32103210Skill

    migrate-to-skills

    Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.

    Also in 4 projects that use this

  • 32103210Skill

    update-cursor-settings

    Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.

    Also in 4 projects that use this

  • Tsumugii24Skill

    split-to-prs

    Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.

    Also in 4 projects that use this

  • +3 more from 0mlkrizzz655335v
  • +2 more from 32103210

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the repo already has a framework (check for playwright.config, pytest.ini, pom.xml, package.json), follow the existing framework, …

    line 15
  2. Distinctive:

    Use the Page Object Model for UI tests once there are more than a couple of tests.

    line 19
  3. Very specific:

    Add a clear test name that describes the scenario: test("login fails with expired password shows reset link").

    line 24
  4. Distinctive:

    Read the manual test case(s) the user provides.

    line 28
  5. Distinctive:

    If no framework exists yet, scaffold a minimal one (config + one example test + README explaining how to run it) and confirm the structure …

    line 29
  6. Distinctive:

    Write the automated tests.

    line 30
  7. Distinctive:

    Never weaken an assertion just to make a test green.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Test Automation Helper

Convert manual test cases into reliable automated tests.

Defaults

  • UI web tests: Playwright with TypeScript (or Python if the user prefers / the repo already uses Python).
  • API tests: pytest + requests (Python) or Playwright APIRequestContext if the project is TS.
  • Mobile tests: Maestro (simple YAML flows) for a quick start, Appium for a full framework — see the mobile-test skill for details.
  • If the repo already has a framework (check for playwright.config, pytest.ini, pom.xml, package.json), follow the existing framework, structure, and naming instead of introducing a new one.

Rules for good tests

  • Use the Page Object Model for UI tests once there are more than a couple of tests.
  • Selectors: prefer getByRole/getByTestId; never brittle XPath with indexes.
  • No sleep/fixed waits — use auto-waiting or explicit waits on conditions.
  • Each test independent: sets up its own data, no dependency on execution order.
  • Assert on outcomes users care about (visible text, status codes, DB state), not implementation details.
  • Add a clear test name that describes the scenario: test("login fails with expired password shows reset link").

Workflow

  1. Read the manual test case(s) the user provides.
  2. If no framework exists yet, scaffold a minimal one (config + one example test + README explaining how to run it) and confirm the structure with the user.
  3. Write the automated tests.
  4. Run them and show the results. If a test fails because the app is not reachable, say so clearly instead of "fixing" the test to pass.
  5. Never weaken an assertion just to make a test green.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.