Automated summary
Generates a test suite derived from Eiffel contracts and runs tests, with AI chain coverage gap analysis.
Strengths
- Fully automated contract-based test generation
- Mandatory zero-warnings policy ensuring code quality
- Integrated coverage analysis to identify gaps
- Saves test evidence for traceability
Limitations
- Requires Phase 4 to be complete (compilable implementation)
- Depends on the quality of written contracts to generate relevant tests
- Does not handle integration or end-to-end testing
Use this skill after implementing contracts to automate test verification and coverage.
Avoid using it if the project does not use Eiffel contracts or if you prefer a manual testing approach.
Security analysis
SafeThe skill runs a specific project build and test command using Bash, which is a legitimate use within a controlled build environment. It does not contain destructive, exfiltrating, or obfuscated instructions, and it does not disable safety features. The risk is limited to user-provided project code, which is inherent to any build system.
No concerns found
How this analysis is madeExamples
/eiffel.verify /path/to/eiffel-project/eiffel.verify ./my-eiffel-appname: eiffel-verify description: Phase 5 of Eiffel Spec Kit. Generates test suite derived from contracts and runs tests. Includes AI chain coverage gap analysis. Use with /eiffel.verify command. allowed-tools: Read, Grep, Glob, Edit, Write, Bash, Task
/eiffel.verify - Phase 5: Test Generation and Verification
Purpose: Flesh out skeletal tests, generate contract-derived tests, verify all tests pass.
Usage
/eiffel.verify <project-path>
Project Scoping
<project-path>/
├── .eiffel-workflow/
│ ├── prompts/
│ │ └── phase5-coverage-review.md
│ └── evidence/
│ ├── phase5-tests.txt
│ └── phase5-coverage.txt
├── test/*.e (tests fleshed out here)
Prerequisites
- Phase 4 complete: implementation compiles
Workflow
Step 1: Flesh Out Skeletal Tests
Complete tests created in Phase 1.
Step 2: Generate Contract-Derived Tests
For each postcondition, ensure a test verifies it.
Step 3: Generate Coverage Review Prompt
Create <project-path>/.eiffel-workflow/prompts/phase5-coverage-review.md:
# Test Coverage Review
## Contracts
[PASTE src/*.e]
## Tests
[PASTE test/*.e]
## Check For:
- Postconditions without corresponding tests
- Edge cases not tested
- Precondition boundary tests missing
Step 4: Compile and Run Tests (MANDATORY GATE)
CRITICAL: You MUST cd to the project directory before compiling. The EIFGENs folder is created in the current working directory, not where the ECF file is located. Compiling from the wrong directory pollutes other folders with build artifacts.
cd <project-path> && /d/prod/ec.sh -batch -config <project>.ecf -target <project>_tests -c_compile
./EIFGENs/<project>_tests/W_code/<project>.exe
ZERO WARNINGS POLICY: If the compiler reports obsolete call warnings or any other warnings, FIX THEM IMMEDIATELY. Do not note them and move on. Do not defer them. Fix them right now before proceeding.
ALL TESTS MUST PASS.
Step 5: Save Evidence
Save to <project-path>/.eiffel-workflow/evidence/phase5-tests.txt:
# Phase 5 Test Evidence
# Project: <project-path>
# Date: [timestamp]
[Paste test output]
Tests run: [count]
Tests passed: [count]
# Status: PASS / FAIL
Context Management (RLM Pattern)
This skill focuses ONLY on: <project-path>
DO NOT:
- Read files outside this project directory
- Load entire ecosystem or multiple libraries into context
- Keep large file contents in working memory
DO:
- Use Task tool with Explore agent for ecosystem questions
- Ask targeted questions when tests need to understand external library behavior
- Release context after getting answers
Example - Ecosystem Query:
Need to understand how simple_testing assertions work? Don't read all its files.
Instead: Task(subagent_type=Explore) → "What assertions does EQA_TEST_SET provide?"
The sub-agent searches, summarizes, and returns ONLY what you need. Your context stays focused on this project.
Completion
Phase 5 COMPLETE: Verification passed.
Project: <project-path>
Tests: [N] passed
Next: Run /eiffel.harden <project-path> for adversarial testing.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/eiffel-test-generation-and-verification-mmh8qqfs/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/eiffel-test-generation-and-verification-mmh8qqfs' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/eiffel-test-generation-and-verification-mmh8qqfs/download' --output '.skill-downloads/eiffel-test-generation-and-verification-mmh8qqfs/SKILL.md.part' && mv '.skill-downloads/eiffel-test-generation-and-verification-mmh8qqfs/SKILL.md.part' '.skill-downloads/eiffel-test-generation-and-verification-mmh8qqfs/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Grep, Glob, Edit, Write, Bash, Task
Original excerpt: Prerequisites
- Phase 4 complete: implementation compiles
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/eiffel-test-generation-and-verification-mmh8qqfs/SKILL.md' && test -s '.skill-downloads/eiffel-test-generation-and-verification-mmh8qqfs/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/eiffel-verify' && cp -R '.skill-downloads/eiffel-test-generation-and-verification-mmh8qqfs' '.claude/skills/eiffel-verify'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/eiffel-test-generation-and-verification-mmh8qqfs'openskills read 'eiffel-test-generation-and-verification-mmh8qqfs'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/eiffel-test-generation-and-verification-mmh8qqfs/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
ClickHouse Performance Comparison
Testing
Evaluate ClickHouse performance test results, check PR performance changes, compare with history, and assess whether a result is actionable.
Analyze CI Performance Reports
Testing
Analyze CI performance comparison reports for a ClickHouse PR. Cross-references master history to distinguish real regressions from flaky tests.
Santa Method
Testing
Multi-agent adversarial verification with two independent reviewers. Output is checked twice and iteratively fixed until both pass before shipping.