Opcode Rigor Audit

Assess opcode test rigor in LovecaSim by filtering telemetry and mapping tests.

1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/trioskosmos/rabukasim --skill opcode-rigor-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Opcode Rigor Audit
Source: https://github.com/trioskosmos/rabukasim/tree/main/.agent/skills/opcode_rigor_audit
Command: npx skills add https://github.com/trioskosmos/rabukasim --skill opcode-rigor-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the lack of deep behavioral correctness in automated testing for game opcodes, ensuring thorough verification beyond basic coverage metrics.

Core Features & Use Cases

  • Telemetry Filtering: Identifies opcodes relying on superficial tests.
  • Test Mapping: Links opcodes to their specialized verification methods.
  • Rigor Assessment: Categorizes tests by their depth of verification (Level 1-3).
  • Gap Identification: Pinpoints opcodes needing more robust "Behavioral Regression" tests.
  • Level 3 Test Creation Guidance: Provides recipes for creating high-rigor tests focusing on interaction cycles, effect ripples, and edge boundaries.
  • One-Shot Ready Principles: Offers heuristics for writing tests that pass on the first attempt, including unified dispatch awareness, ID validation, state sanitization, and visibility.

Quick Start

Use the Opcode Rigor Audit skill to analyze the telemetry logs and identify opcodes with insufficient test rigor.

Frequently Asked Questions about Opcode Rigor Audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve opcode test rigor for game development engines?

To improve opcode test rigor, filter telemetry logs to identify opcodes relying on superficial tests. You can then map opcodes to specialized verification methods and categorize their depth to pinpoint gaps in behavioral regression coverage.

What is the difference between Level 1 and Level 3 opcode verification depth?

Verification depth categorizes tests by behavioral rigor. Level 3 tests provide high-rigor verification focusing on interaction cycles, effect ripples, and edge boundaries, moving beyond the basic coverage metrics of lower levels.

How do I write one-shot ready opcode tests that pass on the first attempt?

To write one-shot ready opcode tests, follow heuristics like unified dispatch awareness, ID validation, state sanitization, and visibility. These principles ensure tests pass on the first attempt by addressing modular interpreter behaviors.

Why does my automated testing report high coverage but miss behavioral regressions in opcodes?

Automated testing often lacks deep behavioral correctness because opcodes rely on superficial tests. You need to assess test rigor by mapping opcodes to specialized verification methods and identifying gaps in high-rigor testing.

Does the Opcode Rigor Audit work with LovecaSim engine telemetry logs?

Yes, the Opcode Rigor Audit assesses and enhances the rigor of opcode tests specifically within the LovecaSim engine by analyzing telemetry logs to identify opcodes with insufficient test rigor.