Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLI
Assigneesstack72

AI agent skipped adversarial review step before smoke testing extension code

Opened by bixu Ā· 4/28/2026Ā· Shipped 4/28/2026

Problem

When authoring extension model code, the swamp-extension-model skill explicitly requires an adversarial self-review (step 6 in the workflow) before running unit tests or smoke tests. The instruction reads:

After writing or significantly modifying extension code, and before running unit tests or smoke tests, read references/adversarial-review.md and self-review against all applicable dimensions. Present findings to the user before proceeding to testing.

During a recent session authoring the @hivemq/honeycomb extension (adding createBurnAlert/deleteBurnAlert methods), the AI agent skipped this step entirely and proceeded directly from code authoring to smoke testing against the live Honeycomb API. The adversarial review was never performed and findings were never presented to the user.

Proposed Solution

Add a hard gate in the skill workflow that forces the agent to pause and explicitly present adversarial review findings to the user before any testing step is allowed. This could be:

  • A checklist item the agent must mark complete (with findings) before the smoke-test step
  • A required swamp extension review CLI command that the agent must run and whose output it must present
  • A prominent WARNING block in the skill markdown that is harder to overlook under momentum

Alternatives

  • Keep the current instruction but make it a numbered checklist item with a checkbox the agent must output explicitly (lower friction, may still be skipped)
  • Add a pre-smoke-test check to the CI workflow that surfaces a reminder if no review comment was recorded

Context

The skip occurred because the session had high momentum (iterating rapidly against a live API), and the adversarial review step sits between code authoring and testing with no hard stop enforcing it. The agent later acknowledged the miss when asked directly.

02Bog Flow
āœ“OPENāœ“TRIAGEDāœ“IN PROGRESSāœ“SHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 3 MOREPR_MERGEDSHIPPED

Shipped

4/28/2026, 2:27:11 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack724/28/2026, 1:34:52 PM

Sign in to post a ripple.