Ami test creator
Must be triggered when new functionality is added and no existing tests cover the changes. Automatically generates tests for modified code.From its SKILL.md
npx -y skills add AnaCataVC/amiga-ia --skill ami-test-creatorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, 365 tokens by cl100k_base, as published. Nobody here has run it
Skill: PR Test Creator
When invoked, act as a Test Automation Engineer to ensure the repository has adequate test coverage before a PR is published.
Workflow
-
Assess Coverage:
- Review the modified or target files (from the PR, working tree, or as specified by the user).
- Scan the repository for corresponding test files (e.g., look for
*test.py,*.spec.js,*_test.go). - Determine if the modified logic is adequately covered by existing tests.
-
Generate Tests (If Needed):
- If tests are missing or insufficient, determine the exact test cases needed.
- CRITICAL: Before writing any tests to disk, you MUST present a summary to the user in the chat explaining what exactly you are going to test, the amount of tests you will write, and any suggested changes to the existing test structure to better cover the new cases.
- Ask for the user's explicit permission to proceed.
- Upon approval, automatically generate the missing tests.
- Use the appropriate testing framework for the project (e.g., pytest, jest, vitest, etc.).
- Create or update the relevant test files. Ensure the tests are functional and cover the happy path and edge cases of the new code.
-
Reporting:
- If tests were created or updated, output the list of test files modified.
- If coverage was already sufficient, output: "TEST COVERAGE SUFFICIENT - NO NEW TESTS NEEDED".
Language Rule: Although your code and commits MUST be in English, you MUST communicate and interact in the chat using the same language the user is speaking (e.g., Spanish, French, etc.).
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most test skills give in 365 tokens
Counted across 964 of the 1,571 authors here whose files we hold, read 2026-08-07
- Close the browser when donein 55 of 964, across 12 files
- Wait for network idle statein 51 of 964, across 6 files
- Launch Chromium in headless modein 49 of 964, across 6 files
- Use descriptive selectors for elementsin 49 of 964, across 6 files
- Run provided scripts with help flag firstin 49 of 964, across 6 files
- Add appropriate explicit waitsin 48 of 964, across 5 files
- Use bundled scripts as black boxesin 46 of 964, across 3 files
- Do not read script source codein 46 of 964, across 3 files
- Use sync playwright for scriptsin 46 of 964, across 3 files
- Inspect dom before executing actionsin 46 of 964, across 3 files
- Run the full test suitein 37 of 964
- Write the failing test firstin 29 of 964, across 23 files
Said here and by no other author read
- review modified target files
- scan repository for test files
- determine existing test coverage adequacy
- present test summary before writing files
- ask explicit permission to proceed
- generate missing tests upon approval
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.