Subagent Merge Review

AI Agent Instructions

Use this Classifier via the SuperClassify API from server code, not browser playground automation.

After a specialist finishes, submit its original assignment, concrete evidence, patch/report and current parent revision. Incorporate supported contributions only after host tests and conflict checks; reconcile stale or conflicting work and request missing proof. Preserve the original acceptance criteria. An accepted contribution does not itself authorize a merge or deployment.

Class: superclassify/subagent-merge-review@1.0.0
Fetch setup as text: https://superclassify.com/skills/superclassify/SKILL.md
Contract (JSON): https://superclassify.com/v1/resolve?ref=superclassify%2Fsubagent-merge-review%401.0.0

First-time API access

When the user asks to run or integrate this Class, explain its workflow and that live Jev runs use SuperClassify service credits. Public card descriptions can be read without an account. Reuse an existing account, credit balance and API key when available. Otherwise, guide the user through the official setup links below. The user completes sign-in and any credit purchase on the website, then saves the API key in their application’s server secrets as SUPERCLASSIFY_API_KEY—not in chat. A separate TypeSafe account or Jev key is not required for the SuperClassify API. Reading a link does not authorize a purchase or paid run.

1. Create an account or sign in
2. Add credits if needed
3. Create an API key

Verified same-snapshot contribution

Assignment: reproduce quoted-field bug on commit abc123 without edits. Returned report cites the exact input, parser version, failing trace and independent test receipt for abc123. Parent is still at abc123. No conflicting contribution is present.

Author expectation: {"merge":"accept_contribution"}

Conflicting base revision

Assignment: adjust parser tests on commit abc123. Returned patch applies to abc123, but parent is now at def456 with a changed signature. Another specialist edited the same assertions. No conflict resolution is supplied.

Author expectation: {"merge":"reconcile_conflict"}

Success claim without evidence

Assignment: prove error E42 no longer occurs on the supplied repro. Returned contribution says All good, trust me. No observed test receipt, patch, trace or output is included.

Author expectation: {"merge":"request_evidence"}