Generate adversarial IR inputs to test retikz JSON and zod contracts.
npx skills add https://github.com/Pionpill/retikz --skill develop-test
Please help me install this Agent Skill. Skill: develop-test Source: https://github.com/Pionpill/retikz/tree/main/.agents/skills/develop-test Command: npx skills add https://github.com/Pionpill/retikz --skill develop-test
It reduces the risk that retikz specs pass while real AI-generated inputs still break the implementation, by systematically hunting for adversarial IR/JSON/zod-contract failures before documentation work begins.
Run the develop-test stage by selecting an ADR still in Proposed state, ensuring lint/tsc/vitest are currently all passing, then prompt the system to generate adversarial vitest cases and report any BLOCKING items.
High-intent search queries and answers about installing and using this skill.
To generate adversarial test cases for zod schema validation, you can use an agentic QA sub-agent to create new IR inputs designed to violate schema invariants and discriminator stability. This approach systematically hunts for contract failures before documentation begins.
The best way to harden JSON round-trip equivalence is to run adversarial self-testing that generates inputs violating AI-facing contracts. This process converts discovered BLOCKING issues into formal vitest cases and iterates until all critical failures are fixed and regression-verified.
Yes, you can use vitest to validate contract stability during alpha development by adding only temporary adversarial test cases. The workflow requires producing structured BLOCKING/WARNING/INFO reports without committing any code, schema, or test changes.
To triage contract validation failures, classify results into BLOCKING (must-fix) and WARNING/INFO (review/backlog) categories based on failure modes like JSON round-trip errors and zod parse clarity. This structured reporting isolates critical issues from minor backlog items.
Your zod parse error lacks clarity because adversarial IR inputs may expose missing edge cases in your ADR-derived specs. An opinion-shifted agent can generate inputs to specifically target and improve zod error clarity and discriminator stability.
No, contract validation testing requires an ADR in Proposed state and a baseline where lint, tsc, and vitest are currently passing. This ensures the adversarial bug hunter has a stable foundation to generate and validate new boundary-breaking cases.
whatwecandoVerify project phase completion by running vitest, eslint, tsc, and verify-phase.sh.
DGouronCoordinate spec-driven refactorings with contract tests and incremental batches.
PionpillTranslate alpha ADR implementation contracts into code and passing Vitest suites.
shinyorgGenerate C# source code for AOT-compliant reflection and property access.
