Integrate Plugin Inline Under Reviewers Section

Done — I moved the panel into GitHub’s PR sidebar and restyled it to blend in as a native section under Reviewers.

• The plugin now mounts directly in .discussion-sidebar, positioned immediately after the Reviewers block instead of floating in the viewport (content.js:272, content.js:309).
• I removed the custom “card” look (fixed position, large borders, shadow, boxed stats) and switched to subtle GitHub-like spacing/typography (content.js:62).
• The section now reads as an inline sidebar item with lightweight controls and no extra visual chrome (content.js:325).
• I removed the in-body Open Source Explorer mentions; the only remaining mention is the subtle footer text: “Powered by the Open Source Explorer” (content.js:346).
• “Not found” copy is now neutral and simple: “No contributor profile found yet.” with a low-key directory link (content.js:414).
• I also ran a syntax check: node --check content.js (passes).

If you want, next I can:

1. Tighten it even further to look exactly like an existing GitHub sidebar item (matching heading size/line-height one-to-one).
2. Apply the same visual changes to bookmarklet.js too so both extension + bookmarklet UIs are consistent.

Perfect — I removed the popup treatment entirely.

• The panel now mounts as a native GitHub sidebar section directly under Reviewers instead of floating (content.js and bookmarklet.js).
• I stripped popup/card chrome (fixed positioning, large borders, shadow, boxed stat rows) and switched to GitHub-like sidebar spacing and color tokens so it blends in.
• I removed inline mentions of “Open Source Explorer” from the body states; the only mention left is the subtle footer line: Powered by the Open Source Explorer.
• I applied the same inline/no-popup behavior to both scripts so extension and bookmarklet match.
• Syntax checks pass: node --check content.js and node --check bookmarklet.js.

If you refresh GitHub and still see the old UI, reload the extension once in chrome://extensions and hard refresh the PR page.

Got it — I just fixed that.

I updated the mount logic so it no longer silently fails when GitHub renders the sidebar late or uses a different sidebar container.

• It now retries mounting for a few seconds if the sidebar isn’t ready yet.
• It now targets the visible right sidebar (not a hidden one) and falls back across GitHub sidebar variants.
• Applied in both content.js and bookmarklet.js.

Please do this once:

1. Reload the extension in chrome://extensions
2. Hard refresh the PR page (Cmd+Shift+R)

If it still doesn’t appear, send me what this returns in DevTools console and I’ll patch immediately:

({  panel: !!document.querySelector("#md-expert-pr-panel"),  sidebar: document.querySelector(".discussion-sidebar, .Layout-sidebar")?.className || null})

Thanks — that screenshot was super helpful.
sidebar: null means your GitHub PR view doesn’t use the old .discussion-sidebar classes, so the previous selector path missed it.

I just patched this again in both content.js and bookmarklet.js:

• Finds the Reviewers section by text/role/testid (not just old sidebar classes).
• Handles newer/alternate GitHub layouts.
• Keeps retrying while GitHub lazily renders the page.
• Falls back to inline placement in the main PR view if no sidebar exists (still not popup style).

Please do this once:

1. Reload extension in chrome://extensions
2. Hard refresh PR page (Cmd+Shift+R)

If it still doesn’t show, run this in console and send me output:

({  styleLoaded: !!document.getElementById("md-expert-pr-style"),  panelMounted: !!document.getElementById("md-expert-pr-panel"),  reviewersTextNodes: [...document.querySelectorAll("h2,h3,h4,[role='heading']")]    .filter(n => (n.textContent || "").trim().toLowerCase() === "reviewers")    .length})

Done — I removed those two links from the contributor card in both places:

• content.js
• bookmarklet.js

Specifically, the GitHub and Market.dev link row is gone now (and related row styling removed).
I also rechecked syntax for both files.

If you want, I can also make the contributor name non-clickable too.

Done — removed “Browse directory” in both files.

• Updated content.js and bookmarklet.js so the not-found state now just shows:
  • No contributor profile found yet.
  • no extra link below it

Syntax checks still pass for both files.

Done — committed and pushed.

• Commit: 230ee91
• Branch: main pushed to origin/main successfully (ed79474..230ee91)

Done — I changed the section heading from Projects to Notable Projects in both:

• content.js
• bookmarklet.js

I left the stats label (Projects count) unchanged.

Done — I added a subtle footer link to https://explore.market.dev (“Open Source Explorer”) in both content.js and bookmarklet.js.

It keeps the muted styling and only underlines on hover. Refresh the PR page to see it.

Done — committed and pushed.

• Commit: 19c69e3
• Pushed: main -> origin/main

Yes, keyboard shortcut navigation is definitely possible in this extension.

Best implementation options:

1. Next/prev by PR list order (recommended) — follows the current GitHub ordering/filter.
2. Next/prev by PR number (+1/-1) — simpler but can jump to closed/missing PRs.

If you want, reply with 1 or 2 and I’ll implement it next (I can use ] for next and [ for previous by default).

Implemented option 1 in the extension (content.js).

• Added keyboard shortcuts on PR detail pages:
  • ] = next PR
  • [ = previous PR
• It follows the PR order from the most recent /pulls list you visited in that repo (so it tracks current list ordering/filtering).
• It wraps around at the ends (last -> first, first -> last).
• It won’t trigger while you’re typing in inputs/textareas/contenteditable fields.

Notes:

• If you open a PR directly (without visiting the PR list first), there may be no cached order yet. Open that repo’s /pulls once, then shortcuts work.
• Not committed/pushed yet. If you want, I can commit and push this change now.

Done — I updated it.

• Arrow key navigation now works on PR pages:
  • -> (ArrowRight) = next PR
  • <- (ArrowLeft) = previous PR
• I kept [ and ] working too, so both options work.
• Added a subtle footer hint under Powered by:
  • View next PR using <- ->

File updated: content.js

Refresh the PR page (hard refresh) to load the new shortcut behavior.

Done — I removed the footer hint and moved navigation to two buttons under the GitHub Code button.

What I changed in content.js:

• Added a nav button row (<- and ->) that mounts directly under the detected Code button.
• Matched width to the Code button dynamically.
• Added a small gap (6px) between the Code button and nav row, and between the two nav buttons.
• Styled buttons to blend with GitHub button styles.
• Wired both buttons to previous/next PR navigation.
• Kept keyboard navigation working too (ArrowLeft / ArrowRight, and [ / ]).

Also removed:

• The “View next PR using <- ->” hint text from the panel.

Reload the extension and hard-refresh the PR page to see it.

Fixed — I adjusted both issues in content.js:

• Buttons are now positioned directly under the Code button (not inline to the right).
• Nav row width is locked to the exact Code button width.
• Kept a small vertical gap.
• Arrow labels are now rendered as plain ASCII "<-" and "->" with monospace styling so they read as single arrow strings cleanly.

I also kept keyboard navigation (ArrowLeft / ArrowRight) working.

Please hard refresh the PR page (Cmd+Shift+R) so the updated content script loads.

Great catch — I fixed both in content.js:

• Arrows now use actual arrow glyphs: ← and → (not <- / -> text combos).
• Button height now matches the detected Code button height exactly.
• Border radius also mirrors the Code button so the shape feels native.
• Arrow centering is tightened with flex centering.

Please hard refresh the PR page (Cmd+Shift+R) and check again. If it’s still 1–2px off on your zoom level, I can add a tiny visual offset tweak.

Yep — here’s the trace from the current state (shareable):

git status --shortM content.js

Key diff trace in content.js:

• Added nav constants/state: NAV_CACHE_KEY, NAV_BUTTONS_ID, nav retry/reposition state.
• Added PR-order cache + navigation logic:
  • normalizePullPath, readNavigationCache, writeNavigationCache, cachePullListOrder
  • getAdjacentPullPath, navigateToAdjacentPull
• Added keyboard nav:
  • ArrowLeft / ArrowRight (plus [ / ])
• Added Code-button anchored nav UI:
  • findCodeButton, ensureNavButtons, retry + viewport reposition listeners
  • Buttons now render as ← and →
  • Width/height/radius derived from the actual Code button
• Added styles for #md-expert-pr-nav-buttons and .md-pr-nav-btn.
• Hooked nav refresh into page lifecycle:
  • init() now binds keyboard + viewport listeners and mounts nav buttons
  • applyCheck() also calls ensureNavButtons().

If you want, I can commit this as a separate “PR navigation controls” commit now.