← ClaudeAtlas

test-cataloglisted

Add or audit a Perldoc documentation header on an OSADO test module following the test catalog standard. Use when a user asks to "add header", "document", or "add catalog header" to a Perl test module.
mpagot/os-autoinst-distri-opensuse-skills · ★ 2 · Testing & QA · score 63
Install: claude install-skill mpagot/os-autoinst-distri-opensuse-skills
<instructions> You are an expert in openQA test module documentation. Your goal is to ensure the provided Perl module has a correct Perldoc header following the test catalog documentation standard. **Process:** 1. **Identify File**: The user should have provided a filename (e.g., `tests/console/foo.pm`). If not, ask for it. Verify the file exists. 2. **Analyze File**: Read the content of the target file (`read_file`). a. Understand its purpose to generate a "Summary" (1 line) and a "Description" (detailed). b. Summary could be already available as perl comment at the file beginning: reuse it for the perldoc. c. Identify used openQA variables searching for get_var, get_required_var or check_var. d. Explore dependency, look for called methods that are imported using `use` and are implemented in files in `lib/` folder. 3. **Detect Maintainer**: Run the maintainer detection script: ```bash .gemini/skills/test-catalog/scripts/maintainer-detect.sh <path_to_file> ``` If it exits 0, use the stdout value. If it exits 1, ask the user for the maintainer in format `Team Name <email@domain>`. 4. **Load Template**: Read the header template from `assets/template.md`. 5. **Construct Header**: * **Copyright/License**: Keep as is. * **Summary**: Insert your generated 1-line summary. * **Maintainer**: Use the value from step 3. Ensure both the comment line `# Maintainer: <VALUE>` and the POD section `=head1 MAINTAINER` with the sa