RubyGems - jekyll-theme-zer0 - Versions diffs - 1.0.0 → 1.1.0 - Mend

jekyll-theme-zer0 1.0.0 → 1.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (10) hide show

checksums.yaml +4 -4
data/CHANGELOG.md +33 -0
data/README.md +4 -4
data/_data/prompts.yml +274 -156
data/_includes/content/intro.html +6 -0
data/scripts/lib/changelog.sh +1 -1
data/scripts/lib/migrate.sh +7 -7
data/scripts/test/lib/test_analyze_commits.sh +20 -0
data/scripts/utils/analyze-commits +6 -6
metadata +1 -1

checksums.yaml CHANGED Viewed

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: eb0abcd4c89fc980be5dc8a2ca5d073a32e248d7bea194c9eb905bd02453f3b4
-  data.tar.gz: 156f5db5110105ad33e03d7e3be40ec8ff56f8d5cdab6c2cd5cdd8ababd190f2
+  metadata.gz: 61d06e485b7f208505ec171ac1d0f9b074124eb972085aaccb7a48957fe4a309
+  data.tar.gz: 8d725ba937bb2cac46d4f30d132380f6bdd24616f7e08f851bf0b8f3b3aa5383
 SHA512:
-  metadata.gz: bd44c6d89e293c8d03e6599ff58cb1cc568e0c9281d360ddc49300ef54b9eb56bc32d8e4508fad22b821b3782d87c6ed8a79c706faf65fbc1e9d1399869c16ac
-  data.tar.gz: b3823b150fccbcd91c52919686e9f904e28945f0e235e52b7d26b0a5407f51e562f682b3efbd2add0a3e30185c513b26070f1941029813bb15b65e9cf9b5445c
+  metadata.gz: a4f72a346e3e8e1bad8affd72e8378d20669b5c937c187cbf1434c394a824ccdb2c303adf2cabd6734b24dac30216d294bb0047754d1c536c56e713ce5930287
+  data.tar.gz: b447257158432ebd4a5c6595af8cb842ac8b420b9624f66ebfc80e5cdc395c0b3074145051babd683675c78dcf00bd911ebb4e93522d19df6c9ab202ca1dcbe5

data/CHANGELOG.md CHANGED Viewed

@@ -1,5 +1,20 @@
 # Changelog
+## [1.1.0] - 2026-04-21
+### Changed
+- Version bump: minor release
+### Commits in this release
+- 3d91006 fix(release): replace ((var++)) with var=$((var + 1)) in release path
+- d33e5e6 feat(intro): refocus Copilot Agent prompts on frontend/CMS workflows (#74)
+## [Unreleased]
+### Fixed
+- **Version-bump workflow no longer crashes on bash 5.x runners.** `scripts/utils/analyze-commits` (and `scripts/lib/changelog.sh`, `scripts/lib/migrate.sh`) used the `((var++))` post-increment idiom. On bash 5.x, when `var` is 0 the expression evaluates to 0 → exit code 1 → `set -euo pipefail` terminates the script silently. macOS bash 3.2 was more forgiving, so the bug only surfaced in CI. Replaced all release-path sites with `var=$((var + 1))`, which always returns 0. Added a static regression check to the unit tests so the pattern can't return.
 ## [1.0.0] - 2026-04-20
 First stable major release. Consolidates the breaking-change installer rewrite
@@ -75,6 +90,24 @@ See [`docs/installation/migration-from-0.x.md`](docs/installation/migration-from
 ## [Unreleased]
+### Changed
+- **Copilot Agent prompts (`_data/prompts.yml`)**: rewritten to focus on
+  frontend/CMS workflows for the Jekyll theme. Replaced the previous
+  general-purpose software-engineering templates with 10 prompts split into
+  two scopes: **Page Improvements** (`improve-page`, `expand-page`,
+  `update-page`, `fix-page`, `seo-optimize`, `accessibility-audit`) that act
+  on the current page, and **Site Improvements** (`ui-ux-improvement`,
+  `new-feature`, `component-enhancement`, `performance-optimization`) for
+  theme-wide changes. Every prompt explicitly references the auto-injected
+  Page Context table.
+- **Intro component (`_includes/content/intro.html`)**: the Copilot Agent
+  dropdown now renders Bootstrap `dropdown-header` section labels and
+  dividers when prompt entries declare a `group`. Entries without a
+  `group` continue to render as plain items (backward compatible).
+- **Docs (`docs/implementation/copilot-agent-prompt-button.md`)**: updated
+  the prompt registry table and YAML schema to document the new `group`
+  field and the new template set.
 ### Added
 - **Roadmap data file**: `_data/roadmap.yml` is now the single source of truth for the project roadmap (versions, status, dates, targets, and feature highlights).
 - **Roadmap generator**: `scripts/generate-roadmap.rb` (and shell wrapper `scripts/generate-roadmap.sh`) renders a Mermaid gantt diagram and summary table from `_data/roadmap.yml` and injects them into `README.md` between `<!-- ROADMAP_MERMAID:START/END -->` and `<!-- ROADMAP_TABLE:START/END -->` markers. Supports `--check` mode for CI drift detection and `--stdout` for previewing.

data/README.md CHANGED Viewed

@@ -2,7 +2,7 @@
 title: zer0-mistakes
 sub-title: AI-Native Jekyll Theme
 description: AI-native Jekyll theme for GitHub Pages — Docker-first development, AI-powered installation, multi-agent integration (Copilot, Codex, Cursor, Claude), AI preview-image generation, and AIEO content optimization with Bootstrap 5.3.
-version: 1.0.0
+version: 1.1.0
 layout: landing
 tags:
   - jekyll
@@ -20,7 +20,7 @@ categories:
   - bootstrap
   - ai-tooling
 created: 2024-02-10T23:51:11.480Z
-lastmod: 2026-04-21T04:05:24.000Z
+lastmod: 2026-04-21T05:41:17.000Z
 draft: false
 permalink: /
 slug: zer0
@@ -1066,7 +1066,7 @@ git push origin feature/awesome-feature
 | Metric | Value |
 |--------|-------|
-| **Current Version** | 1.0.0 ([RubyGems](https://rubygems.org/gems/jekyll-theme-zer0), [CHANGELOG](/CHANGELOG)) |
+| **Current Version** | 1.1.0 ([RubyGems](https://rubygems.org/gems/jekyll-theme-zer0), [CHANGELOG](/CHANGELOG)) |
 | **Documented Features** | 43 ([Feature Registry](https://github.com/bamr87/zer0-mistakes/blob/main/_data/features.yml)) |
 | **Setup Time** | 2-5 minutes ([install.sh benchmarks](https://github.com/bamr87/zer0-mistakes/blob/main/install.sh)) |
 | **Documentation Pages** | 70+ ([browse docs](/pages/)) |
@@ -1117,6 +1117,6 @@ And these AI partners that make zer0-mistakes truly AI-native:
 **Built with ❤️ — and a little help from our AI partners — for the Jekyll community**
-**v1.0.0** • [Changelog](CHANGELOG.md) • [License](LICENSE) • [Contributing](CONTRIBUTING.md) • [AI Agent Guide](AGENTS.md)
+**v1.1.0** • [Changelog](CHANGELOG.md) • [License](LICENSE) • [Contributing](CONTRIBUTING.md) • [AI Agent Guide](AGENTS.md)

data/_data/prompts.yml CHANGED Viewed

@@ -1,184 +1,302 @@
 # _data/prompts.yml
-# Prompt templates for the Copilot Agent issue button in the intro section.
-# Each entry maps to a .github/prompts/*.prompt.md file.
-# The body is included in the GitHub issue when that prompt is selected.
-- id: article-review
-  label: "Article Review"
-  icon: "bi-file-text"
-  description: "Review article structure, metadata, and SEO"
+#
+# Prompt templates for the Copilot Agent issue button rendered by
+# `_includes/content/intro.html`. Each entry becomes a dropdown item that
+# opens a pre-filled GitHub issue assigned to @copilot.
+#
+# These templates are tuned for a Jekyll/CMS theme (zer0-mistakes) and focus
+# on FRONTEND and CONTENT (CMS) improvements. Two scopes are supported via
+# the `group` field:
+#
+#   - "Page Improvements" – act on the page the button was clicked from.
+#     The Page Context table injected by intro.html (title, URL, file path,
+#     layout, collection, tags, etc.) is what every prompt should reference.
+#
+#   - "Site Improvements" – act on theme-wide UI/UX, components, layouts,
+#     navigation, performance, or new features. The page is included as the
+#     example/entry point, not necessarily the only target.
+#
+# Schema:
+#   - id:          unique slug
+#     label:       short text shown in the dropdown
+#     icon:        Bootstrap Icons class (https://icons.getbootstrap.com/)
+#     group:       optional section header in the dropdown
+#     description: optional one-line subtitle under the label
+#     body:        prompt instructions appended above the auto-generated
+#                  Page Context + Environment tables in the issue body.
+# ─────────────────────────────────────────────────────────────────────────────
+# Page Improvements — scoped to the current page
+# ─────────────────────────────────────────────────────────────────────────────
+- id: improve-page
+  label: "Improve Page"
+  icon: "bi-stars"
+  group: "Page Improvements"
+  description: "Polish content, structure, and presentation of this page"
   body: |
-    Act as an Expert Content Editor and SEO Specialist.
-    Review this article, validate its structure/metadata, and suggest content expansions to improve depth and engagement.
-    **Review Checklist:**
-    - Front Matter: `title`, `description`, `categories`, `tags`, `date`, `layout` present and valid
-    - Content depth: flag sections that are too brief or superficial
-    - Clarity: identify jargon needing explanation
-    - Structure: verify logical flow with proper H2/H3 headings
-    - SEO: keyword placement in title, H1, and first paragraph
-    - Tone: professional, authoritative, yet accessible
+    Act as a Senior Content Editor and Frontend Designer for the
+    zer0-mistakes Jekyll theme.
+    Improve the page referenced in the **Page Context** table below. Make it
+    clearer, more engaging, and visually consistent with the rest of the
+    site — without changing its core message or breaking existing links.
+    **Scope (this page only):**
+    - Tighten copy: remove fluff, fix grammar, improve readability
+    - Strengthen the opening hook and the closing call-to-action
+    - Verify heading hierarchy (single H1, logical H2/H3 nesting)
+    - Confirm front matter is complete: `title`, `description`, `date`,
+      `lastmod`, `layout`, `categories`, `tags`, `permalink`, `preview`
+    - Improve visual rhythm: paragraph length, lists, callouts, code blocks
+    - Validate internal links and image paths (use `relative_url`)
+    - Ensure Bootstrap 5 utility classes are used over custom CSS
     **Deliverables:**
-    - Front Matter pass/fail report with specific fixes
-    - Bullet-point content issues
-    - Suggested expanded sections (provide actual text)
-- id: code-implementation
-  label: "Code Implementation"
-  icon: "bi-code-slash"
-  description: "Implement a feature with production-ready code"
+    - A diff-style proposal of the edited Markdown (front matter + body)
+    - A short "Why these changes" rationale (3–5 bullets)
+    - A checklist of any follow-up items that are out of scope
+- id: expand-page
+  label: "Expand Page"
+  icon: "bi-arrows-angle-expand"
+  group: "Page Improvements"
+  description: "Add depth, examples, and missing sections to this page"
   body: |
-    Act as a Senior Software Engineer with expertise in clean code practices, design patterns, and production-ready development.
+    Act as a Subject Matter Expert and Technical Writer.
-    Implement the requested feature, module, or system component for this page/file.
+    Expand the page referenced in the **Page Context** table below by adding
+    depth, real examples, and any sections that a reader would reasonably
+    expect but are currently missing.
-    **Requirements:**
-    - Follow existing code conventions and style
-    - Include error handling and edge cases
-    - Add inline documentation and comments
-    - Write unit tests if applicable
-    - Consider performance and security implications
+    **Expansion targets:**
+    - Add concrete, copy-pasteable examples (code, configs, screenshots)
+    - Add a "Prerequisites" and "Next steps" / "Related" section
+    - Add a short FAQ or troubleshooting block when relevant
+    - Cross-link to related posts, docs, or theme components in this repo
+    - Add or update Mermaid diagrams where they clarify flow/architecture
+    - Keep the existing tone, structure, and front matter intact
     **Deliverables:**
-    - Complete, working implementation
-    - Explanation of design decisions
-    - Test cases
-    - Usage examples
-- id: code-refactoring
-  label: "Code Refactoring"
-  icon: "bi-arrow-repeat"
-  description: "Refactor code for quality, readability, and performance"
+    - The new/expanded Markdown sections, ready to merge into the page
+    - A list of any new assets needed (images, diagrams, data files)
+    - Suggested updates to `tags`, `categories`, and `description`
+- id: update-page
+  label: "Update Page"
+  icon: "bi-arrow-clockwise"
+  group: "Page Improvements"
+  description: "Refresh outdated content, versions, links, and screenshots"
   body: |
-    Act as a Code Quality Expert and Refactoring Specialist.
-    Refactor the code in this file to improve quality, maintainability, and performance while preserving exact external behavior.
-    **Refactoring Goals:**
-    - Apply SOLID principles and clean code practices
-    - Eliminate duplication (DRY)
-    - Improve naming clarity
-    - Reduce complexity and nesting
-    - Optimize performance bottlenecks
+    Act as a Documentation Maintainer responsible for keeping the
+    zer0-mistakes site accurate and current.
+    Audit and update the page referenced in the **Page Context** table below.
+    Treat any version numbers, dates, screenshots, or external references as
+    suspect and verify them against the current state of the repository and
+    the wider ecosystem.
+    **Update checklist:**
+    - Bump version numbers, release names, and dependency references
+    - Replace deprecated Jekyll/Bootstrap patterns with current equivalents
+    - Refresh screenshots, GIFs, and embedded examples
+    - Re-validate every external link; replace dead or moved URLs
+    - Update `lastmod` in the front matter and add a brief "Updated" note
+    - Reconcile content with related files in this repo (configs, layouts,
+      includes) so instructions match what the codebase actually does
     **Deliverables:**
-    - Refactored code with before/after comparison
-    - Explanation of each change and its rationale
-    - Any breaking changes or migration notes
+    - Updated Markdown for the page (front matter + body)
+    - A short changelog summarising what was refreshed and why
+    - Any follow-up issues to file for changes outside this page
-- id: debugging
-  label: "Debugging"
+- id: fix-page
+  label: "Fix Page Issue"
   icon: "bi-bug"
-  description: "Diagnose and fix issues in the code"
+  group: "Page Improvements"
+  description: "Report a typo, broken link, layout glitch, or content bug"
   body: |
-    Act as a Senior Debugging Specialist and Software Troubleshooting Expert.
+    Act as a Frontend QA Engineer for the zer0-mistakes Jekyll theme.
-    Analyze the provided code, error messages, and symptoms to identify the root cause and propose a targeted fix.
+    Investigate and fix the issue described below on the page referenced in
+    the **Page Context** table. Reproduce it locally with `docker-compose up`
+    before proposing a change.
-    **Please provide in your response:**
-    - Root cause analysis (WHY it fails, not just WHAT)
-    - Targeted fix with code changes
-    - Verification steps to confirm the fix
-    - Preventive measures to avoid recurrence
+    **Please describe (fill in before submitting):**
+    - **What is wrong?** <!-- typo, broken link, image, layout, behaviour -->
+    - **Where on the page?** <!-- section heading, line, screenshot region -->
+    - **Expected:** <!-- what should appear / happen -->
+    - **Actual:** <!-- what currently appears / happens -->
+    - **Browser / device (if visual):** <!-- e.g. Chrome 124 desktop, iOS Safari -->
-    **Steps to reproduce:** <!-- fill in below -->
+    **Deliverables:**
+    - Root-cause analysis (content vs. layout vs. include vs. config)
+    - Minimal, surgical fix (Markdown, Liquid, SCSS, or front matter)
+    - Verification steps and a passing `bundle exec jekyll build`
+- id: seo-optimize
+  label: "SEO Optimize"
+  icon: "bi-graph-up-arrow"
+  group: "Page Improvements"
+  description: "Improve discoverability, metadata, and structured data"
+  body: |
+    Act as a Technical SEO Specialist.
-    **Expected behavior:** <!-- fill in below -->
+    Optimise the page referenced in the **Page Context** table below for
+    search engines and social sharing, without sacrificing readability.
-    **Actual behavior / error message:** <!-- fill in below -->
+    **Audit and improve:**
+    - Front matter `title` (≤ 60 chars) and `description` (150–160 chars)
+    - Primary keyword in H1, first paragraph, and at least one H2
+    - `permalink` is short, lowercase, and hyphen-separated
+    - `tags` and `categories` align with site taxonomy
+    - `preview` image exists, has descriptive alt text, and good aspect ratio
+    - Open Graph + Twitter Card metadata via existing includes
+    - JSON-LD structured data (Article / BlogPosting) where applicable
+    - Internal links to high-value related pages, with descriptive anchors
-- id: documentation
-  label: "Documentation"
-  icon: "bi-journal-text"
-  description: "Generate or improve technical documentation"
+    **Deliverables:**
+    - Updated front matter
+    - Specific in-body edits (H1/H2/intro)
+    - A keyword/intent map (primary + 3–5 secondary)
+    - Any sitemap, robots, or `_config.yml` changes required
+- id: accessibility-audit
+  label: "Accessibility Audit"
+  icon: "bi-universal-access"
+  group: "Page Improvements"
+  description: "Audit this page for WCAG 2.1 AA compliance"
   body: |
-    Act as a Technical Writer and Documentation Specialist.
-    Create or improve the documentation for the code, API, or content in this file.
-    **Documentation Scope:**
-    - Purpose and overview
-    - Installation / setup instructions
-    - Usage examples with code snippets
-    - API reference (parameters, return values, errors)
-    - Troubleshooting / FAQ section
-    **Standards:**
-    - Clear, concise language
-    - Consistent formatting (Markdown)
-    - Working code examples
-    - Proper heading hierarchy
-- id: requirements-analysis
-  label: "Requirements Analysis"
-  icon: "bi-list-check"
-  description: "Convert ideas into structured technical requirements"
+    Act as an Accessibility (a11y) Engineer.
+    Audit the page referenced in the **Page Context** table below against
+    WCAG 2.1 AA and propose concrete fixes in Markdown, Liquid, or SCSS.
+    **Audit areas:**
+    - Semantic HTML and heading order
+    - Alt text on every meaningful image; empty alt on decorative ones
+    - Sufficient colour contrast (≥ 4.5:1 body, ≥ 3:1 large text/UI)
+    - Keyboard navigability and visible focus states
+    - ARIA attributes on Bootstrap components (modals, dropdowns, tabs)
+    - Form labels, error messages, and `aria-describedby` associations
+    - Skip links and landmark regions (`<main>`, `<nav>`, `<aside>`)
+    - Reduced-motion and prefers-color-scheme respect
+    **Deliverables:**
+    - Findings table: issue, WCAG criterion, severity, fix
+    - Patches for the page and any shared includes that need updating
+    - A re-test plan (axe-core, Lighthouse, manual keyboard pass)
+# ─────────────────────────────────────────────────────────────────────────────
+# Site Improvements — theme-wide UI/UX, components, and features
+# ─────────────────────────────────────────────────────────────────────────────
+- id: ui-ux-improvement
+  label: "UI/UX Improvement"
+  icon: "bi-palette"
+  group: "Site Improvements"
+  description: "Propose a design or UX refinement for the theme"
   body: |
-    Act as an expert Business Analyst and Technical Lead.
-    Analyze the content of this page and convert it into a comprehensive, structured technical requirements document.
-    **Output Structure:**
-    - Executive Summary
-    - Functional Requirements (user stories + acceptance criteria)
-    - Non-Functional Requirements (performance, security, scalability)
-    - Technical Constraints and Assumptions
-    - Out of Scope items
-    - Open Questions
-- id: system-design
-  label: "System Design"
-  icon: "bi-diagram-3"
-  description: "Design a scalable system architecture"
+    Act as a Senior UI/UX Designer working in Bootstrap 5 and Jekyll.
+    Propose a UI/UX improvement for the zer0-mistakes theme. Use the page
+    referenced in the **Page Context** table below as the starting example;
+    where the change applies site-wide, call that out explicitly.
+    **Cover in your proposal:**
+    - **Problem / opportunity** — what user pain or quality gap exists?
+    - **Affected surfaces** — layouts, includes, components, or data files
+    - **Design direction** — spacing, typography, colour, motion, hierarchy
+    - **Bootstrap-first approach** — utilities and components over custom CSS
+    - **Responsive behaviour** — xs / sm / md / lg / xl / xxl breakpoints
+    - **Accessibility** — contrast, focus, ARIA, reduced-motion
+    - **Dark mode / colour scheme** considerations
+    - **Before/after sketch or description** of the change
+    **Deliverables:**
+    - A concrete change list mapped to files in `_layouts/`, `_includes/`,
+      `_sass/`, and `assets/`
+    - SCSS / Liquid / HTML snippets ready to drop in
+    - A short test plan covering desktop + mobile + keyboard
+- id: new-feature
+  label: "New Feature"
+  icon: "bi-lightbulb"
+  group: "Site Improvements"
+  description: "Propose a new site-wide feature or capability"
   body: |
-    Act as a Senior Software Architect.
-    Design a comprehensive system architecture based on the requirements or content described in this page.
-    **Design Deliverables:**
-    - High-level architecture diagram (described in text/Mermaid)
-    - Component breakdown and responsibilities
-    - Data models and API contracts
-    - Security and authentication strategy
-    - Scalability and reliability considerations
-    - Technology stack recommendations with rationale
-- id: test-generation
-  label: "Test Generation"
-  icon: "bi-check2-square"
-  description: "Generate comprehensive tests for code"
+    Act as a Product Manager + Frontend Engineer for the zer0-mistakes
+    Jekyll theme.
+    Propose a new feature for the site or theme. Use the page referenced in
+    the **Page Context** table below as the inspiration / first consumer of
+    the feature where it makes sense.
+    **Please describe:**
+    - **User story** — As a [reader / author / theme adopter], I want…
+    - **Problem solved** and the success metric
+    - **Scope** — pages, layouts, includes, data files, configs touched
+    - **Configuration** — what goes into `_config.yml` / `_data/*.yml`?
+    - **Dependencies** — any new gems, JS libs, or vendor assets?
+    - **Privacy / analytics** — does it need consent gating?
+    - **Rollout plan** — feature flag, opt-in via front matter, default-on?
+    - **Out of scope** items
+    **Deliverables:**
+    - A minimal, working implementation plan (file-by-file)
+    - Sample Liquid / HTML / SCSS / JS scaffolding
+    - Documentation stub for `docs/` or `pages/_docs/`
+    - CHANGELOG entry following Keep a Changelog format
+- id: component-enhancement
+  label: "Component Enhancement"
+  icon: "bi-puzzle"
+  group: "Site Improvements"
+  description: "Improve a Jekyll layout, include, or shared component"
   body: |
-    Act as a QA Automation Engineer and Test Architect.
-    Generate a comprehensive test suite for the code or functionality described in this file.
-    **Test Coverage:**
-    - Unit tests for core logic
-    - Integration tests for component interactions
-    - Edge cases and error conditions
-    - Performance benchmarks (if applicable)
-    **Standards:**
-    - Follow existing test framework conventions
-    - Clear test descriptions
-    - Arrange-Act-Assert pattern
-    - Mocks/stubs for external dependencies
-- id: prompt-engineering
-  label: "Prompt Engineering"
-  icon: "bi-lightning"
-  description: "Craft an effective AI prompt for this task"
+    Act as a Senior Jekyll Theme Developer.
+    Enhance a shared component used by the page referenced in the
+    **Page Context** table below — a layout in `_layouts/`, an include in
+    `_includes/`, or a partial in `_sass/`. Improvements should benefit every
+    page that uses the component, not just this one.
+    **Targets to consider:**
+    - Cleaner Liquid: safe `default:` filters, fewer nested `if`s
+    - Parameterise hard-coded values via `include.*` arguments
+    - Consistent BEM-style class names and Bootstrap utility usage
+    - Add the standard component header comment block
+    - Improve mobile responsiveness and accessibility
+    - Document parameters and usage in the file header
+    **Deliverables:**
+    - The enhanced file(s), preserving backward compatibility
+    - A migration note if any include parameters changed
+    - Before/after rendering notes for at least one page that uses it
+    - A test plan: `docker-compose exec jekyll bundle exec jekyll build`
+- id: performance-optimization
+  label: "Performance Optimization"
+  icon: "bi-speedometer2"
+  group: "Site Improvements"
+  description: "Improve load time, Core Web Vitals, and asset delivery"
   body: |
-    Act as an expert Prompt Engineer specializing in software development and AI-assisted workflows.
+    Act as a Web Performance Engineer.
-    Craft a high-quality, effective prompt that will guide an AI agent to work on the content or task described in this page.
+    Profile and optimise the site, using the page referenced in the
+    **Page Context** table below as a representative measurement target.
-    **Prompt Requirements:**
-    - Clear role definition (Act as...)
-    - Specific task instructions
-    - Input/output format specification
-    - Constraints and edge cases
-    - Example inputs and expected outputs
-    - Quality criteria for evaluation
+    **Investigate:**
+    - Core Web Vitals: LCP (Largest Contentful Paint), CLS (Cumulative
+      Layout Shift), and INP (Interaction to Next Paint) for this page
+    - Render-blocking CSS/JS in `_includes/core/head.html` and `js-cdn.html`
+    - Vendored Bootstrap and Bootstrap Icons under `assets/vendor/`
+    - Image strategy: dimensions, `loading="lazy"`, modern formats
+    - Liquid hot spots: nested loops, repeated `where` filters
+    - Build output size in `_site/` and unused CSS
+    **Deliverables:**
+    - Lighthouse / WebPageTest results before and after
+    - Specific patches to layouts, includes, SCSS, and config
+    - Any new build steps or scripts (must be opt-in, GitHub Pages-safe)
+    - A short report on tradeoffs and follow-ups

data/_includes/content/intro.html CHANGED Viewed

@@ -96,7 +96,13 @@
         <span class="d-none d-sm-inline ms-1">Copilot Agent</span>
       </button>
       <ul class="dropdown-menu dropdown-menu-end" aria-labelledby="copilotAgentDropdown">
+        {% assign current_group = "" %}
         {% for prompt in site.data.prompts %}
+        {% if prompt.group and prompt.group != current_group %}
+        {% unless forloop.first %}<li><hr class="dropdown-divider"></li>{% endunless %}
+        <li><h6 class="dropdown-header">{{ prompt.group }}</h6></li>
+        {% assign current_group = prompt.group %}
+        {% endif %}
         {% capture issue_title %}[{{ prompt.label }}] {{ page.title }}{% endcapture %}
         {% capture issue_body %}{{ prompt.body }}
 ---

data/scripts/lib/changelog.sh CHANGED Viewed

@@ -137,7 +137,7 @@ generate_changelog() {
     while IFS='|' read -r hash subject author date; do
         [[ -z "$hash" ]] && continue
-        ((commit_count++))
+        commit_count=$((commit_count + 1))
         # Skip merge commits
         if echo "$subject" | grep -qE "^Merge (branch|pull request|remote-tracking branch)"; then

data/scripts/lib/migrate.sh CHANGED Viewed

@@ -146,18 +146,18 @@ install_admin_pages() {
         if [[ ! -f "$template_file" ]]; then
             warn "Template not found: $template_file — skipping"
-            ((skipped++))
+            skipped=$((skipped + 1))
             continue
         fi
         if [[ -f "$output_file" ]] && [[ "$force" != "true" ]]; then
             info "Already exists (use --force to overwrite): $output_file"
-            ((skipped++))
+            skipped=$((skipped + 1))
             continue
         fi
         dry_run_exec "Render ${page}.md" render_template "$template_file" "$output_file"
-        ((installed++))
+        installed=$((installed + 1))
         debug "Installed: $output_file"
     done
@@ -193,24 +193,24 @@ verify_admin_pages() {
     local page page_file
     for page in "${ADMIN_PAGES[@]}"; do
         page_file="$output_dir/${page}.md"
-        ((total++))
+        total=$((total + 1))
         if [[ ! -f "$page_file" ]]; then
             warn "Missing: $page_file"
-            ((errors++))
+            errors=$((errors + 1))
             continue
         fi
         # Check required front matter fields
         if ! grep -q 'layout: admin' "$page_file" 2>/dev/null; then
             warn "Missing 'layout: admin' in $page_file"
-            ((errors++))
+            errors=$((errors + 1))
             continue
         fi
         if ! grep -q 'permalink:' "$page_file" 2>/dev/null; then
             warn "Missing 'permalink' in $page_file"
-            ((errors++))
+            errors=$((errors + 1))
             continue
         fi

data/scripts/test/lib/test_analyze_commits.sh CHANGED Viewed

@@ -107,3 +107,23 @@ tmp=$(mktemp -d)
 ) && assert_true "true" "Logs are written to stderr" \
    || assert_true "false" "Logs are written to stderr"
 rm -rf "$tmp"
+echo -e "\nTesting safety against ((var++)) + set -e crash on bash 5.x..."
+# Regression test: in bash 5.x, ((var++)) when var is 0 returns exit code 1,
+# which under `set -euo pipefail` (used by both the analyzer and the CI workflow
+# step that calls it) terminates the script silently. The fix is to use
+# var=$((var + 1)) which always returns 0. This static check ensures we never
+# reintroduce the ((var++)) pattern in the release-path scripts.
+if grep -qE '\(\([a-zA-Z_][a-zA-Z0-9_]*\+\+\)\)' "$ANALYZER"; then
+    assert_true "false" "analyze-commits is free of ((var++)) post-increments"
+else
+    assert_true "true"  "analyze-commits is free of ((var++)) post-increments"
+fi
+CHANGELOG_LIB="$(cd "$SCRIPT_DIR/../../lib" && pwd)/changelog.sh"
+if grep -qE '\(\([a-zA-Z_][a-zA-Z0-9_]*\+\+\)\)' "$CHANGELOG_LIB"; then
+    assert_true "false" "changelog.sh is free of ((var++)) post-increments"
+else
+    assert_true "true"  "changelog.sh is free of ((var++)) post-increments"
+fi

data/scripts/utils/analyze-commits CHANGED Viewed

@@ -110,17 +110,17 @@ analyze_commit() {
             # Critical/breaking change files (MAJOR)
             if echo "$file" | grep -qE "(Gemfile|gemspec|_config\.yml|docker-compose\.yml|Dockerfile)$"; then
-                ((critical_files++))
+                critical_files=$((critical_files + 1))
                 log_debug "Critical file detected: $file"
             # Feature files (MINOR)
             elif echo "$file" | grep -qE "(_layouts/|_includes/|assets/|pages/.*\.md$|\.rb$|\.js$)"; then
-                ((feature_files++))
+                feature_files=$((feature_files + 1))
                 log_debug "Feature file detected: $file"
             # Documentation and minor files (PATCH)
             elif echo "$file" | grep -qE "(README|CHANGELOG|\.md$|\.txt$|\.yml$|\.yaml$|test/)"; then
-                ((patch_files++))
+                patch_files=$((patch_files + 1))
                 log_debug "Patch file detected: $file"
             fi
         done <<< "$commit_files"
@@ -171,17 +171,17 @@ determine_overall_bump() {
         case "$bump_level" in
             "major")
-                ((major_count++))
+                major_count=$((major_count + 1))
                 highest_bump="major"
                 ;;
             "minor")
-                ((minor_count++))
+                minor_count=$((minor_count + 1))
                 if [[ "$highest_bump" != "major" ]]; then
                     highest_bump="minor"
                 fi
                 ;;
             "patch")
-                ((patch_count++))
+                patch_count=$((patch_count + 1))
                 if [[ "$highest_bump" == "none" ]]; then
                     highest_bump="patch"
                 fi

metadata CHANGED Viewed

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: jekyll-theme-zer0
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.1.0
 platform: ruby
 authors:
 - Amr Abdel