zipper

Guide the agent through a structured 4-phase process (Explore, Synthesize, Validate, and Issue/Reject) to systematically deepen codebase architecture.

Auto Review closeout. Runs as parallel review subagents inside the current coding agent (Claude Code or Cursor) — no external reviewer CLI.

Use when the same agent mistake, review finding, mutation survivor, or CI failure appears twice, or when spot-checking recently merged PRs, to turn the pattern into a permanent constraint instead of another prose rule.

Use when the user asks what keeps going wrong, after a session where the agent needed repeated correction, or before hardening the environment, to mine past OpenCode sessions in this repository for recurring corrections.

Run functional QA for Zipper. Maps the git diff to CLI flows, tests the built application through Droid Control, and writes a concise QA report. Use when testing PRs, releases, or local changes.

QA tests for the Zipper CLI. Exercises Standard, Loadfile-Only, Chaos Engine, Production Set, Source-Driven Generation, Load File Formats, Archive Test Fixtures, Production Manifest comparison, version output, and CLI boundaries.

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies

Use when about to claim a Zipper change is done, fixed, or passing, especially for CLI behavior, Load File formats, Production Sets, or output bytes, to gather real-artifact evidence before the claim.