Skip to content

Vinix24/vnx-orchestration / skills/quality-engineer

quality-engineer

Verified

Quality validation specialist covering functional, performance, and security testing to ensure production readiness through evidence-based testing.

FileKindSize
SKILL.mdskill md2.2 KB
references/_MAPPING.mdmarkdown432 B
template.mdmarkdown1.7 KB

template.md

View on GitHub
# Quality Engineer Report Template

## Output Location
Write your report to: `$VNX_DATA_DIR/unified_reports/`

## Filename Format
`{timestamp}-{track}-quality-{title}.md`

Example: `20260202-143000-B-quality-api-validation.md`

## Report Structure

### Summary
Brief overview of quality validation work completed (2-3 sentences)

### Tags (Required)
- [tag1, tag2, tag3]  # Use specific, compound tags (e.g., sse-streaming, browser-pool, kvk-validation). Avoid general-only tags.

### Test Strategy
- Testing approach taken
- Test types executed (unit, integration, E2E)
- Risk areas assessed
- Dutch market compliance checks

### Quality Assessment
- Code quality score and methodology
- Coverage metrics (unit, integration)
- Performance validation against budgets
- Security scan results

### Issues Found
- Critical issues (blockers)
- Major issues (must fix before release)
- Minor issues (improvements)

### Evidence
- Test output and pass/fail statistics
- Coverage reports
- Performance benchmark results
- Security scan output

### Open Items
<!-- List any unfinished work, blockers, or issues discovered -->
<!-- Format: - [ ] [severity] Title (optional details) -->
<!-- Severities: [blocker], [warn], [info] -->
<!-- Leave empty if all work completed -->

### Recommendations
- Quality gate pass/fail decision
- Additional testing needed
- Technical debt items identified
- Process improvements

### Intelligence Feedback
<!-- If your dispatch included [INTELLIGENCE_DATA] with offered_pattern_hashes, report which patterns you actually used: -->
used_pattern_hashes: []

## Quality Standards
- Minimum 80% unit test coverage
- All critical paths validated
- Performance within budget constraints
- No critical/high security issues
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall