Atmos Tests
cloudposse/atmos
Author Atmos smoke tests, post-deployment stack checks, and integration tests using type: test, HTTP assertions, shell or script/interpreter checks, require gates, parallel dependencies, matrix…
Generates comprehensive test scenarios from requirements including BDD/Gherkin scenarios, unit tests, integration tests, and end-to-end test cases.
$ npx skills add ArabelaTso/Skills-4-SE --skill req-to-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ArabelaTso/Skills-4-SE req-to-test --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/req-to-test .claude/skills/req-to-test && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "req-to-test" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/req-to-test into .claude/skills/req-to-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "req-to-test", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/req-to-testType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ArabelaTso/Skills-4-SE --skill req-to-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ArabelaTso/Skills-4-SE req-to-test --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/req-to-test .agents/skills/req-to-test && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "req-to-test" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/req-to-test into .agents/skills/req-to-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "req-to-test", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ArabelaTso/Skills-4-SE --skill req-to-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ArabelaTso/Skills-4-SE req-to-test --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/req-to-test .cursor/skills/req-to-test && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "req-to-test" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/req-to-test into .cursor/skills/req-to-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "req-to-test", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ArabelaTso/Skills-4-SE.git --path skills/req-to-test--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ArabelaTso/Skills-4-SE --skill req-to-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ArabelaTso/Skills-4-SE req-to-test --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/req-to-test .gemini/skills/req-to-test && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "req-to-test" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/req-to-test into .gemini/skills/req-to-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "req-to-test", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ArabelaTso/Skills-4-SE req-to-testInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ArabelaTso/Skills-4-SE --skill req-to-test -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/req-to-test .github/skills/req-to-test && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "req-to-test" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/req-to-test into .github/skills/req-to-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "req-to-test", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ArabelaTso/Skills-4-SE --skill req-to-test -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ArabelaTso/Skills-4-SE req-to-test --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/req-to-test .opencode/skills/req-to-test && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "req-to-test" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/req-to-test into .opencode/skills/req-to-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "req-to-test", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
req-to-testGenerates comprehensive test scenarios from requirements including BDD/Gherkin scenarios, unit tests, integration tests, and end-to-end test cases.
Req To Test is an agent skill from ArabelaTso/Skills-4-SE. Generates comprehensive test scenarios from requirements including BDD/Gherkin scenarios, unit tests, integration tests, and end-to-end test cases. Use when converting requirements, user stories, or specifications into testable scenarios with full coverage including happy paths, error cases, edge cases, and boundary conditions. Outputs structured test suites ready for implementation.
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files and assets (for example `assets/test_suite_template.json`, `references/coverage_checklist.md` and `references/test_patterns.md`).
It sits in Testing & QA, covering Test generation, Integration testing and Unit testing. The repository describes itself as: A curated list of 180+ useful Claude Skills for Software Engineering and resources for customizing AI for SE workflows. The licence is Apache-2.0.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 4f38503. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are gherkin and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Req To Test loads about 2.9k tokens when it runs, and up to ~7.1k if it reads all its reference files. Until then it costs about 100 tokens; SKILL.md has 701 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from ArabelaTso/Skills-4-SE at commit 4f38503, republished under its Apache-2.0 licence (© ArabelaTso). 701 words, ~2,896 tokens.
.claude/skills/req-to-test/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.You are an expert test engineer who transforms requirements into comprehensive, executable test scenarios.
This skill enables you to:
Follow this process when generating test scenarios from requirements:
Read each requirement and identify:
For each requirement, decide which test types are needed:
BDD/Gherkin Scenarios - Use for:
Unit Tests - Use for:
Integration Tests - Use for:
E2E Tests - Use for:
For each test type, use the patterns in references/test_patterns.md:
Structure scenarios as:
Feature: User Registration
As a new user
I want to create an account
So that I can access the platform
Scenario: Successful registration with valid credentials
Given I am on the registration page
And I am not logged in
When I enter email "user@example.com"
And I enter password "SecurePass123"
And I click "Register"
Then I see "Registration successful"
And I am redirected to the dashboard
And a confirmation email is sent to "user@example.com"
Scenario: Registration fails with invalid email
Given I am on the registration page
When I enter email "invalid-email"
And I enter password "SecurePass123"
And I click "Register"
Then I see error "Please enter a valid email address"
And I remain on the registration page
And no account is createdGenerate test cases with clear structure:
Test Suite: User Registration Validation
Test: test_validate_email_accepts_valid_format
Setup: None required
Input: email = "user@example.com"
Execute: result = validate_email(email)
Assert: result == True
Test: test_validate_email_rejects_invalid_format
Setup: None required
Input: email = "invalid-email"
Execute: result = validate_email(email)
Assert: result == False
Test: test_validate_email_rejects_empty_string
Setup: None required
Input: email = ""
Execute: result = validate_email(email)
Assert: result == False
Test: test_create_user_with_valid_data
Setup:
- Initialize database connection
- Clear users table
Input:
- email = "user@example.com"
- password = "SecurePass123"
Execute: user = create_user(email, password)
Assert:
- user.email == "user@example.com"
- user.password is hashed
- user.created_at is set
- user.id is generated
Cleanup: Delete test userDesign integration tests:
Test: User Registration API Integration
Setup:
- Start test server
- Initialize test database
- Configure email service mock
Steps:
1. POST /api/register with valid credentials
2. Verify API returns 201 Created
3. Verify response contains user ID and token
4. Query database for new user record
5. Verify email service was called with correct parameters
Assertions:
- API response status: 201
- Response body contains: {id: <uuid>, token: <jwt>}
- Database contains user with email "user@example.com"
- User password is hashed (not plain text)
- Email service called with subject "Welcome"
- Confirmation link in email contains valid token
Cleanup:
- Delete test user from database
- Stop test serverCreate complete user journeys:
Test: Complete User Registration and Login Journey
Scenario: New user registers and logs in successfully
Given browser opens application homepage
And no user exists with email "newuser@example.com"
When user clicks "Sign Up" button
Then registration page is displayed
When user enters email "newuser@example.com"
And user enters password "SecurePass123"
And user enters password confirmation "SecurePass123"
And user clicks "Create Account"
Then success message "Account created successfully" appears
And user is redirected to dashboard at "/dashboard"
And welcome message displays "Welcome, newuser@example.com"
When user logs out
Then user is redirected to homepage
When user clicks "Sign In"
And user enters email "newuser@example.com"
And user enters password "SecurePass123"
And user clicks "Log In"
Then user is redirected to dashboard
And session is active
Verification:
- User account persists in database
- User can access protected resources
- Session cookie is set correctlyUse the references/coverage_checklist.md to verify coverage:
Happy Path Coverage:
Error Path Coverage:
Edge Case Coverage:
Example - Comprehensive coverage for "Age" field (must be 18-65):
Happy Path:
- age = 25 (valid middle value)
- age = 18 (minimum boundary)
- age = 65 (maximum boundary)
Error Cases:
- age = 17 (below minimum)
- age = 66 (above maximum)
- age = -5 (negative)
- age = 0 (zero)
- age = "twenty" (invalid type)
- age = null (missing)
- age = "" (empty string)
- age = 999999 (extremely large)
Edge Cases:
- age = 17.9 (decimal below minimum)
- age = 18.0 (decimal at minimum)
- age = 65.1 (decimal above maximum)Classify each test by priority:
Critical (P0):
High (P1):
Medium (P2):
Low (P3):
Organize test scenarios clearly:
# Test Suite: [Feature Name]
## Overview
- Source Requirements: REQ-001, REQ-002
- Total Scenarios: 15
- Coverage: Happy path, Error cases, Edge cases
## BDD Scenarios
### Critical Priority
Feature: User Authentication
Scenario: Successful login with valid credentials [P0]
Scenario: Login fails with incorrect password [P0]
### High Priority
Feature: User Authentication
Scenario: Login fails with non-existent user [P1]
Scenario: Account locks after 5 failed attempts [P1]
## Unit Tests
### Module: auth.validators
Test: test_validate_password_strength_accepts_strong_password [P1]
Test: test_validate_password_strength_rejects_weak_password [P1]
Test: test_validate_password_strength_requires_minimum_length [P1]
## Integration Tests
Test: Authentication API returns JWT token on successful login [P0]
Test: Authentication API rate limits after repeated failures [P1]
## E2E Tests
Test: User can register, login, and access protected resources [P0]
Test: User session expires after timeout [P1]
## Test Data
Valid Credentials:
- email: "valid.user@example.com"
- password: "SecurePass123!"
Invalid Credentials:
- email: "invalid@example.com" (non-existent)
- password: "wrong" (incorrect)
## Coverage Summary
- Requirements Covered: 5/5 (100%)
- Happy Path: 5 scenarios
- Error Cases: 8 scenarios
- Edge Cases: 7 scenarios
- Total: 20 test scenarios"User must be able to..." → BDD scenario + E2E test "System shall validate..." → Unit test for validator + BDD for user feedback "Data must be..." → Unit test for data constraint + Integration test for persistence "API endpoint..." → Integration test for API contract "When X happens, Y should..." → BDD scenario for behavior + Unit test for logic
For each requirement, generate:
Provide test scenarios in requested format:
Gherkin/BDD - For human-readable acceptance tests
JSON - For test automation frameworks (use assets/test_suite_template.json)
Markdown - For documentation and review
Code snippets - For specific testing frameworks (Jest, PyTest, etc.)
When format not specified, provide Markdown with all test types included.
references/test_patterns.md - Detailed patterns for each test typereferences/coverage_checklist.md - Comprehensive coverage checklistassets/test_suite_template.json - JSON template for structured output© ArabelaTso, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (references, assets) in skills/req-to-test of ArabelaTso/Skills-4-SE.
Open the folder on GitHubat commit 4f38503
Req To Test next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Req To Test this skillArabelaTso/Skills-4-SE | 253 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Atmos Testscloudposse/atmos | 1.4k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Memstack Development Test Writercwinvestments/memstack | 423 | — | ~3.7k | Automated safety check: Pass | Proprietary | |
| Frappe Testing UnitImpertio-Studio/Frappe_Claude_Skill_Package | 187 | — | ~3k | Automated safety check: Pass | MIT | |
| Testing Safe Protocolarchibate/dotfiles-opencode | 108 | — | ~3.2k | Automated safety check: Notes | None | |
| Test Experteinverne/dotfiles | 121 | — | ~2.3k | Automated safety check: Pass | GPL-3.0 |
cloudposse/atmos
Author Atmos smoke tests, post-deployment stack checks, and integration tests using type: test, HTTP assertions, shell or script/interpreter checks, require gates, parallel dependencies, matrix…
cwinvestments/memstack
A skill your agent uses when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with…
Impertio-Studio/Frappe_Claude_Skill_Package
A skill your agent uses when writing unit tests, integration tests, creating test fixtures, or running tests with bench run-tests.
archibate/dotfiles-opencode
Safe testing practices to prevent real-world side-effects. An agent skill from archibate/dotfiles-opencode.
einverne/dotfiles
Testing methodologies, test-driven development (TDD), unit and integration testing, and testing best practices across multiple frameworks.
aiskillstore/marketplace
This skill should be used when writing tests, validating features, or needing to verify code works.
ArabelaTso/Skills-4-SE
Generate prioritized CVE watchlists and actionable security recommendations for repositories.
ArabelaTso/Skills-4-SE
Automatically migrate Python web applications between frameworks (Flask → FastAPI, Django → FastAPI).
ArabelaTso/Skills-4-SE
Generate test cases using metamorphic testing by applying transformations based on metamorphic properties.
ArabelaTso/Skills-4-SE
Instruments programs to capture execution traces specifically for reproducing reported bugs, enabling consistent replay and diagnosis of failures.
ArabelaTso/Skills-4-SE
Automatically migrate Spring MVC applications to Spring Boot.
ArabelaTso/Skills-4-SE
Instrument programs (Python, C/C++, Java) to capture snapshots of key program states at runtime, including variables, memory, and call stacks.
Categories
Generates comprehensive test scenarios from requirements including BDD/Gherkin scenarios, unit tests, integration tests, and end-to-end test cases. Req To Test is an agent skill from ArabelaTso/Skills-4-SE. Generates comprehensive test scenarios from requirements including BDD/Gherkin scenarios, unit tests, integration tests, and end-to-end test cases.
Req To Test fits situations like: converting requirements; specifications into testable scenarios with full coverage including happy paths; boundary conditions.
Run `npx skills add ArabelaTso/Skills-4-SE --skill req-to-test -a claude-code`. Or copy the skill folder (skills/req-to-test in ArabelaTso/Skills-4-SE) into .claude/skills/req-to-test in your project. Claude Code loads it when a task matches its description.
Run `npx skills add ArabelaTso/Skills-4-SE --skill req-to-test -a codex`. Or copy the skill folder (skills/req-to-test in ArabelaTso/Skills-4-SE) into .agents/skills/req-to-test in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ArabelaTso/Skills-4-SE --skill req-to-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/req-to-test, .gemini/skills/req-to-test, .github/skills/req-to-test and .opencode/skills/req-to-test in your project.
SKILL.md names no scripts, command-line tools or credentials: Req To Test is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Req To Test is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.2k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Req To Test: Atmos Tests (cloudposse/atmos, 1.4k stars), Memstack Development Test Writer (cwinvestments/memstack, 423 stars), Frappe Testing Unit (Impertio-Studio/Frappe_Claude_Skill_Package, 187 stars) and Testing Safe Protocol (archibate/dotfiles-opencode, 108 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
ArabelaTso (a GitHub user) maintains it in ArabelaTso/Skills-4-SE, which has 253 GitHub stars. The repository holds 150 skills in this directory. The repository was last updated on August 21, 2026.
Source: ArabelaTso/Skills-4-SE on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.