Our review
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
Examples
/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.
TDD Red-Green-Refactor
Testing
Skill that guides Claude through the complete TDD cycle.
Web Accessibility Audit
Testing
Performs a comprehensive web accessibility audit following WCAG standards.
UAT Test Case Generator
Testing
Generates structured and comprehensive user acceptance test cases.