GitHub Issue Template Quick Filler

WHAT IT DOES This script transforms GitHub issue templates into a user-friendly side panel with labeled input fields. When you create or edit an issue on GitHub, the script detects the template structure (marked with HTML comments like or headers like "## Steps to Reproduce") and displays each section as a separate textarea in a floating panel. You can fill in each section, and the script automatically inserts your content back into the issue body textarea in the correct template format. No more scrolling through markdown to find the right section to edit—each template part has its own dedicated field. A "Clear all" button lets you reset all fields at once, and the script saves your fill history locally so you can reuse previous entries. WHERE IT RUNS The script runs on GitHub issue creation pages (github.com/*/*/issues/new*) and issue editing pages (github.com/*/*/issues/*/edit). It works on both desktop and mobile views, and updates dynamically as you switch between the "Write" and "Preview" tabs. HOW TO USE After installation, the settings panel appears on the left side of the screen with the gear emoji (⚙️). Open the panel to configure the script: - The "Enable quick filler" toggle enables or disables the script. - The "History" section shows how many entries are saved. Click "Clear history" to remove all saved entries. - Click "Refresh template" to re-scan the page and rebuild the filler panel. When you open an issue creation or editing page, the filler panel appears on the right side of the screen. Each template section has a labeled textarea. Fill in the fields, and the issue body updates automatically. Use the "Fill Template" button to manually trigger an update. Use "Clear All" to reset all fields. Click the "History" button to load a previous fill. TECHNICAL SECTION — REAL MECHANISM The script detects issue pages by checking the URL for /issues/new or /issues/*/edit. It finds the issue body textarea using selectors like #issue_body, textarea[name="issue[body]"], and .js-comment-field. The template is parsed by scanning the textarea's content line by line. It looks for HTML comments () and markdown headers (## or ###) to identify template sections. When a section marker is found, the script captures all following lines until the next marker, storing them as the initial content for that field. The filler panel is created as a fixed-position div with a glassmorphism style, containing textarea inputs for each section. Each input is bound to an input event that triggers an update of the issue body. The update function reconstructs the template by combining the field labels and input values, and writes the result back to the textarea using the native value setter and dispatching "input" and "change" events for React's event system. Fill history is stored as an array of complete issue body strings via GM_setValue, with a limit of 20 entries. THE PANEL The settings panel is built with BotGentz's BGPanel component. It is draggable via its header, allowing you to reposition it anywhere on the screen. The panel snaps to the left edge by default but can be moved freely. Click the gear emoji to collapse the panel into a small bubble, and click the bubble to expand it again. The panel remembers its position per page session. Press the Escape key to quickly close or minimize the panel. The panel includes a status flash bar that provides visual feedback when settings are changed or actions are performed. All settings and history save automatically via GM_setValue. PLEASE NOTE This script requires the free BotGentz browser extension to run. It does not function as a standalone Chrome extension and does not use chrome.* APIs. GitHub frequently updates its issue creation and editing interface, which may affect the selectors used to find the textarea or the template parsing logic. If the script stops working, please check for updates. The script works with both markdown and plain text templates, but template parsing is based on common patterns—custom template structures may not be fully supported. The script stores only your preferences and fill history via GM_setValue. No data is sent externally—all data is stored locally in your browser. The script never reads or writes password fields, hidden inputs, or file inputs. All DOM operations use safe methods (style properties, textContent, appendChild) and never use innerHTML.