ruclo
17 verified skills
v3/skills/v3-generate-std
# Skill: /v3-generate-std > _This document was created with the assistance of Claude (Anthropic)._ You are a Senior QE Engineer responsible for creating Software Test Descriptions (STDs) for OpenShift Virtualization. Given a high-level Software Test Plan (STP), generate test code stubs with comprehensive docstrings that serve as the STD. **Important:** The generated test code should follow the structure and patterns from the [openshift-virtualization-tests](https://github.com/RedHatQE/openshi
development
v3/skills/v3-test-heal
# Skill: /v3-test-heal **Purpose**: Self-healing loop that runs the generated test against a real cluster, analyzes failures from logs, consults documentation and repository code to fix issues, and records lessons learned in GRAVEYARD.md ## Input - **Required**: Path to the generated test file (e.g., `tests/virt/cluster/test_vnc_screenshot.py`) - **Optional**: `--max-iterations N` - Maximum heal attempts (default: 3) ## Output - **Modified File**: Test file edited in-place with fixes applied
development
v3/skills/v3-pyright-heal
# Skill: /v3-pyright-heal **Purpose**: Universal Python type checker and self-healing fixer for ANY Python file ## Input - **Required**: Path to Python file (`.py` or `.ipynb`) - **Optional**: `--max-iterations N` - Maximum fix attempts (default: 10) - **Optional**: `--strict` - Use strict type checking mode ## Output - **Modified File**: Same file, edited in-place - **Exit Code**: 0 if clean, 1 if max iterations reached with errors - **Log**: Summary of fixes applied ## Implementation ###
development
v2.1/skills/v2.1-explore-test-context
# Skill: /v2.1-explore-test-context **Purpose**: Discover repository-specific testing patterns, utilities, fixtures, and conventions ## Input - **Required**: Repository root (implicit - current working directory) ## Output - **No file artifacts** - findings are reported in conversation and used for subsequent code generation - **Format**: Verbal summary of discovered patterns, utilities, fixtures, and conventions ## Role You are exploring the test repository to understand its structure, patt
development
v2.1/skills/v2.1-generate-pytest
# Skill: /v2.1-generate-pytest **Purpose**: Generate executable pytest code from Software Test Description (STD) using repository context ## Input - **Required**: Path to STD markdown file - **Prerequisite**: Repository context should be explored using `/v2.1-explore-test-context` first - **Optional**: `--output-dir` - target directory (default: infer from repository conventions) ## Output - **File**: `test_<feature_name>.py` - **Location**: Determined by repository conventions (e.g., `tests/
development
v2.1/skills/v2.1-generate-std
# Skill: /v2.1-generate-std > _This document was created with the assistance of Claude (Anthropic)._ You are a Senior QE Engineer responsible for creating Software Test Descriptions (STDs) for OpenShift Virtualization. Given a high-level Software Test Plan (STP), generate test code stubs with comprehensive docstrings that serve as the STD. **Important:** The generated test code should follow the structure and patterns from the [openshift-virtualization-tests](https://github.com/RedHatQE/opens
development
v2.1/skills/v2.1-pyright-heal
# Skill: /v2.1-pyright-heal **Purpose**: Universal Python type checker and self-healing fixer for ANY Python file ## Input - **Required**: Path to Python file (`.py` or `.ipynb`) - **Optional**: `--max-iterations N` - Maximum fix attempts (default: 10) - **Optional**: `--strict` - Use strict type checking mode ## Output - **Modified File**: Same file, edited in-place - **Exit Code**: 0 if clean, 1 if max iterations reached with errors - **Log**: Summary of fixes applied ## Implementation ##
development
v2.2/skills/v2.2-explore-test-context
# Skill: /v2.2-explore-test-context **Purpose**: Discover repository-specific testing patterns, utilities, fixtures, and conventions ## Input - **Required**: Repository root (implicit - current working directory) ## Output - **File**: `context.json` - **Format**: Structured JSON containing: ```json { "utilities": { "classes": ["ClassName", ...], "methods": ["method_name", ...], "constants": ["CONSTANT_NAME", ...] }, "fixtures": { "common": ["fixture_name", ...], "sco
development
v2.2/skills/v2.2-generate-pytest
# Skill: /v2.2-generate-pytest **Purpose**: Generate executable pytest code from Software Test Description (STD) and repository context ## Input - **Required**: Path to STD markdown file - **Required**: Path to context.json (from `/v2.2-explore-test-context`) - **Optional**: `--output-dir` - target directory (default: infer from context) ## Output - **File**: `test_<feature_name>.py` - **Location**: Determined by context conventions (e.g., `tests/<domain>/<feature>/`) - **Format**: Executable
development
v2.2/skills/v2.2-generate-std
# Skill: /v2.2-generate-std > _This document was created with the assistance of Claude (Anthropic)._ You are a Senior QE Engineer responsible for creating Software Test Descriptions (STDs) for OpenShift Virtualization. Given a high-level Software Test Plan (STP), generate test code stubs with comprehensive docstrings that serve as the STD. **Important:** The generated test code should follow the structure and patterns from the [openshift-virtualization-tests](https://github.com/RedHatQE/opens
development
v2.2/skills/v2.2-pyright-heal
# Skill: /v2.2-pyright-heal **Purpose**: Universal Python type checker and self-healing fixer for ANY Python file ## Input - **Required**: Path to Python file (`.py` or `.ipynb`) - **Optional**: `--max-iterations N` - Maximum fix attempts (default: 10) - **Optional**: `--strict` - Use strict type checking mode ## Output - **Modified File**: Same file, edited in-place - **Exit Code**: 0 if clean, 1 if max iterations reached with errors - **Log**: Summary of fixes applied ## Implementation ##
development
v2/skills/v2-explore-test-context
# Skill: /v2-explore-test-context **Purpose**: Discover repository-specific testing patterns, utilities, fixtures, and conventions ## Input - **Required**: Repository root (implicit - current working directory) ## Output - **No file artifacts** - findings are reported in conversation and used for subsequent code generation - **Format**: Verbal summary of discovered patterns, utilities, fixtures, and conventions ## Role You are exploring the test repository to understand its structure, patter
development
v2/skills/v2-generate-pytest
# Skill: /v2-generate-pytest **Purpose**: Generate executable pytest code from Software Test Plan (STP) using repository context ## Input - **Required**: Path to STP markdown file - **Prerequisite**: Repository context should be explored using `/v2-explore-test-context` first ## Output - **File**: `test_<feature_name>.py` - **Location**: Appropriate directory based on repository conventions ## Role Act as a Senior SDET. You will translate a Software Test Plan (STP) into an executable Python
development
v2/skills/v2-pyright-heal
# Skill: /v2-pyright-heal **Purpose**: Universal Python type checker and self-healing fixer for ANY Python file ## Input - **Required**: Path to Python file (`.py` or `.ipynb`) - **Optional**: `--max-iterations N` - Maximum fix attempts (default: 10) - **Optional**: `--strict` - Use strict type checking mode ## Output - **Modified File**: Same file, edited in-place - **Exit Code**: 0 if clean, 1 if max iterations reached with errors - **Log**: Summary of fixes applied ## Implementation ###
development
v3/skills/v3-explore-test-context
# Skill: /v3-explore-test-context **Purpose**: Discover repository-specific testing patterns, utilities, fixtures, conventions, and learn from past mistakes documented in GRAVEYARD.md ## Input - **Required**: Repository root (implicit - current working directory) ## Output - **No file artifacts** - findings are reported in conversation and used for subsequent code generation - **Format**: Verbal summary of discovered patterns, utilities, fixtures, conventions, and past mistakes ## Role You a
development
v3/skills/v3-generate-pytest
# Skill: /v3-generate-pytest **Purpose**: Generate executable pytest code from Software Test Description (STD) using repository context ## Input - **Required**: Path to STD markdown file - **Prerequisite**: Repository context should be explored using `/v3-explore-test-context` first - **Optional**: `--output-dir` - target directory (default: infer from repository conventions) ## Output - **File**: `test_<feature_name>.py` - **Location**: Determined by repository conventions (e.g., `tests/<dom
development
v3/skills/v3-graveyard-verify
# Skill: /v3-graveyard-verify **Purpose**: Post-generation verification that cross-references the generated test code against GRAVEYARD.md to catch known mistakes before runtime ## Input - **Required**: Path to the generated test file ## Output - **Modified File**: Test file edited in-place with fixes for any GRAVEYARD violations found - **Report**: Summary of violations found and fixes applied (conversational output) ## Role You are a **code reviewer specializing in catching known mistakes*
development