feat(skills): add 5-skill suite (recon, inventory, explore, screenshot-all, diff)#121
Open
HermeticOrmus wants to merge 2 commits into
Open
feat(skills): add 5-skill suite (recon, inventory, explore, screenshot-all, diff)#121HermeticOrmus wants to merge 2 commits into
HermeticOrmus wants to merge 2 commits into
Conversation
…be-diff Four new skills that complement vibe-check + vibe-explore: - vibe-recon: maps a web app's auth wall + edge surface without logging in. Edge curl, redirect chain, security headers, navigates the landing page, captures any visible login DOM, pulls the SPA bundle for grep-based route discovery. The "look but don't touch" mode. - vibe-inventory: walks every visible route a SPA declares, captures per-route status (200 / /error / 404), screenshots each, and grep the JS bundle for API endpoints, permission tokens, and role names. Produces a structural feature map. Login-aware via --auth-required. - vibe-screenshot-all: pure visual catalog mode. Walks routes from the bundle, screenshots each, builds a contact-sheet HTML for stakeholder review or visual regression baselines. No DOM probe, no clicking. - vibe-diff: compares two vibe-inventory snapshots and surfaces what changed — new/removed routes, new/removed API endpoints, new/removed permission tokens, version bump, bundle-size delta. No browser, pure file-based diff. Useful for periodic re-inventories during a long-running rebuild or vendor audit. Each skill is self-contained: SKILL.md frontmatter + bash runner + helper JS where needed. Binary resolution mirrors vibe-check's pattern (vibium → ./clicker/bin/vibium → ./node_modules/.bin/vibium). Smoke-tested vibe-recon against https://raven-eye.app: pulls the 10.7 MB Vite bundle, finds 280 API endpoints across 60 domains, 25 React Router route patterns. The bundle-grep regex required a fix to avoid matching /assets/manifest.json as /assets/manifest.js (require non-word boundary after .js).
…ilities vibe-explore is the inverse of vibe-check: instead of executing a known plan against a known UI, it clicks every safe interactive element on the page and reports what each one does, then produces a ranked "what you can do here" report. Hard safety filter on by default — skips delete/submit/pay/sign-out/ send/post/checkout patterns, form submits, external-origin links, and target=_blank anchors. --include-destructive lifts the filter. Includes a 4-strategy consent-banner dismissal (visible-button-text → vendor-specific Usercentrics/OneTrust/Cookiebot → shadow-DOM walk → force-hide-CSS) so the click loop runs on real-world consent-walled sites. Smoke-tested against https://github.com/VibiumDev/vibium: 143 clickables found, 123 safe, 7/8 clicks landed real outcomes including mega-menu disclosures and intra-site navigation. Completes the skill suite (vibe-recon → vibe-inventory → vibe-explore → vibe-screenshot-all → vibe-diff) alongside the existing vibe-check.
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
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.
Why
vibe-checkcovers the "execute a known plan against a known UI" use case. This PR adds five complementary skills for the workflows Vibium users hit before and around that:vibe-reconvibe-inventoryvibe-explorevibe-screenshot-allvibe-diffEach skill is self-contained —
SKILL.md+ bash runner + helper JS where needed. Binary resolution mirrorsvibe-check's pattern (vibium→./clicker/bin/vibium→./node_modules/.bin/vibium). No Go binary changes; pure-additive PR.What changed
+18 files, ~830 lines, 0 existing files modified.
vibe-recon — auth-wall + edge mapping (no login)
Edge curl, redirect chain, security headers, navigates the landing page, captures any visible login DOM, pulls the SPA bundle for grep-based route discovery. Read-only mode for "look but don't touch."
vibe-inventory — structural feature map
Walks every route the SPA bundle declares (capped at
--max-routes, default 30), captures per-route status / tables / grids / inputs / buttons, screenshots each, and grep the bundle for/api/*endpoints + permission tokens (Word:Word:Word) + role names. Login-aware via--auth-required(pause for manual sign-in).vibe-explore — click safe elements + rank capabilities
Inverse of
vibe-check: clicks every safe interactive element on the page, classifies each outcome (navigation / modal / inline-disclosure / external / noop / route-error), screenshots before+after, then produces a ranked "what you can do here" report.Hard safety filter on by default — skips
delete/submit/pay/sign-out/send/post/checkoutpatterns, form submits, external-origin links,target=_blankanchors.--include-destructivelifts the filter.Includes a 4-strategy consent-banner dismissal (visible-button-text → vendor-specific Usercentrics/OneTrust/Cookiebot → shadow-DOM walk → force-hide-CSS). Required to make the click loop work on real-world consent-walled sites.
vibe-screenshot-all — visual catalog
One PNG per route + a contact-sheet HTML for stakeholder review or visual regression baselines. No DOM probe, no clicking.
vibe-diff — what changed between two snapshots
Pure file-based diff between two
vibe-inventoryrun dirs. Surfaces new/removed routes, new/removed API endpoints, new/removed permission tokens, version bump, bundle-size delta. No browser, no daemon — justcommanddiffagainst the artifacts.How to test
Each skill ships a self-contained bash runner. Smoke tests run against public sites, no login required:
All bash scripts pass
bash -n; all JS helpers passnew Function(code)parse.vibe-reconend-to-end againsthttps://raven-eye.appproduces 280 API endpoints across 60 domains, 25 React Router patterns.vibe-exploreend-to-end againsthttps://github.com/VibiumDev/vibiumproduces 7/8 clicks landing real outcomes including mega-menu disclosures.Notes
vibe-recon + vibe-inventory + vibe-screenshot-all + vibe-difffirst, thenvibe-exploresecond; happy to squash if preferred.bundle-grep.shregex/assets/<name>.jswas matching/assets/manifest.jsontruncated to.json greedy-prefix engines. Fix requires a non-word boundary after.js(commitce7df57).vibe-explorewas originally a separate branch (feature/vibe-explore-skill); consolidated into this suite branch and the standalone branch retired.SKILL.mdfiles are the agent-facing one-pagers (matchingvibe-check's style); the bash runners are what an operator would invoke directly.vibiumandjq— both already required by other parts of the repo or trivially installable.