Gate retool-import skills on the deterministic compatibility policy#6
Open
rsuresh-retool wants to merge 1 commit into
Open
Gate retool-import skills on the deterministic compatibility policy#6rsuresh-retool wants to merge 1 commit into
rsuresh-retool wants to merge 1 commit into
Conversation
Run import-policy.mjs as a Compatibility gate in both the generic retool-import skill and the lovable specialization, before any discovery or handoff. hard_no app types are blocked locally with parity copy; Next.js (soft_no) gets a best-effort confirm; supported apps proceed. Reconcile the prereq framework note (next/gatsby/expo) with the gate, which is now authoritative on app-type support. Retool's R2 agent remains the fallback for the non-skills path. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
frankyj3578
approved these changes
Jun 5, 2026
frankyj3578
left a comment
frankyj3578
left a comment
There was a problem hiding this comment.
Acc to unblock, have you tested this locally?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Wires the deterministic classifier from the base PR (#5) into both import skills as a Compatibility gate, run right after the prerequisites check and before any discovery or handoff.
retool-import/SKILL.mdandretool-import-lovable/SKILL.mdnow runimport-policy.mjsand act on the verdict:hard_no→ blocked locally with parity copy + docs link; skill ends.soft_no(Next.js carve-out) → best-effort confirm HITL; proceeds onyand records the approval under Open questions; stops otherwise.supported→ proceeds silently.nodemissing / script error → don't silently skip; confirm with user (R2 agent re-validates as fallback).next/gatsby/expowere implied supported) — the prereq check is now explicitly just "is this a JS frontend repo," and the gate is authoritative on app-type support (gatsby/expo → hard_no, next → soft_no).Why
Gives the local agent parity with the browser import's compatibility policy so unsupported app types are rejected before submitting to R2. Folded into the existing prerequisites step in both files to avoid renumbering the
step Ncross-references.Note
The local gate mirrors Retool's pre-agent layer exactly, including the Next.js carve-out ordering — so
Next.js + unsupported-backendresolves tosoft_nolocally, identical to the browser pre-agent classifier. Retool's agent-sideevaluate_app_compatibility(full polyglot bucket mapping) catches that combination and remains the fallback.🤖 Generated with Claude Code