The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

content/en/docs/applications/nats.md (1)

4-6: Provide an explicit numeric weight

Same issue as in FerretDB page.

-weight: 
+weight: 0

content/en/docs/applications/kafka.md (1)

4-6: Empty weight front-matter

Please set an explicit integer or drop the key.

-weight: 
+# weight: 10   # example

content/en/docs/applications/mysql.md (1)

4-6: Specify weight explicitly

Same remark as for the other application docs.

-weight: 
+weight: 0

content/en/docs/virtualization/resources.md (1)

4-4: Trailing comma still present – YAML will parse but is noisy
This was flagged earlier; keeping the comma serves no purpose and can confuse future diffs.

-description: "Reference for VM Instance Types and Instance Profiles,"
+description: "Reference for VM Instance Types and Instance Profiles"

content/en/docs/networking/_index.md (1)

1-8: Add a trailing newline to satisfy POSIX tools

The file lacks a terminating newline. Some linters and diff viewers complain about this.

-This documentation section explains network configuration, virtual routers, load balancers, and other networking capabilities in Cozystack.
+This documentation section explains network configuration, virtual routers, load balancers, and other networking capabilities in Cozystack.
+

content/en/docs/virtualization/_index.md (1)

2-4: linkTitle duplicates the page below – rename to avoid sidebar confusion

This was raised in a previous review but is still unresolved. Keeping two items with identical “Virtual Machines” labels (the section index and virtual-machines.md) confuses users.

-title: "Virtual Machines in Cozystack"
-linkTitle: "Virtual Machines"
+title: "Virtualization in Cozystack"
+linkTitle: "Virtualization"

content/en/docs/guides/bundles/_index.md (1)

38-40: Same broken landing page as flagged earlier
The reference [vm] still points to /docs/virtualization, which is empty.
See previous review — please update to /docs/virtualization/virtual-machines for a meaningful target.

content/en/docs/_index.md (1)

11-12: Confirm alias path format & add trailing-slash variant

Hugo treats “pretty URLs” as directory paths ending with a /. An alias without the trailing slash (/docs/reference) will generate a redirect HTML file at /docs/reference/index.html, but incoming links that include the trailing slash (/docs/reference/) will not be redirected unless a second alias is declared.

Consider adding the slash-terminated variant to avoid 404s and preserve existing inbound links:

 aliases:
   - /docs/reference
+  - /docs/reference/

content/en/docs/applications/mysql.md (3)

25-26: Typo in placeholder – <instnace>

-kubectl edit mariadb <instnace>
+kubectl edit mariadb <instance>

---

61-64: Multiple typos in “Known issues” list

• “can't not be finished” → “cannot be finished”
• “finised” → “finished”
• “inmplemented” → “implemented”

Please correct for professionalism and clarity.

---

66-72: Misspelling of “indices”

-**Corrupted indicies**
+**Corrupted indices**

content/en/docs/applications/rabbitmq.md (1)

4-6: Confirm weight/null handling & keep metadata explicit

weight: is currently set to YAML null (empty).
In Hugo this evaluates to 0, which may unexpectedly pin the page to the top of its section.
If the intent is to defer ordering to section defaults, consider omitting the key altogether; otherwise give it an explicit integer.

-weight: 
+# weight: 30      # ← example value

Same for any other newly-added application docs for consistency.

content/en/docs/applications/postgres.md (1)

4-6: Unclear ordering – provide concrete weight or drop the key

Leaving weight: empty serialises as null → 0.
Give an explicit value or remove the key so Hugo falls back to alphabetic sorting.

-weight: 
+# weight: 40

(Replicate across other app pages if needed.)

content/en/docs/networking/mikrotik.md (1)

5-7: Alias looks good; use trailing slash only if old site had it

The new alias /docs/operations/virtualization/mikrotik will 301 old links.
If legacy URLs ever ended with a trailing slash, add a second alias to cover it:

   - /docs/operations/virtualization/mikrotik
+  - /docs/operations/virtualization/mikrotik/

Minor but prevents a 404 for bookmarked paths.

content/en/docs/applications/clickhouse.md (1)

4-7: Fill in empty description & weight for better SEO / ordering

An empty description diminishes search-engine snippets and on-site previews; add a concise summary (≤ 160 chars).
Also decide on a concrete weight or omit the field as noted in earlier comments.

-description: ""
-weight: 
+description: "High-performance column-oriented OLAP DBMS with managed backups, sharding and scaling."
+# weight: 35

content/en/docs/applications/_include/kafka.md (1)

1-7: Provide a concrete weight or drop the field

weight: is left blank. Hugo treats an empty value as null, which is valid YAML but may lead to non-deterministic ordering in section menus. Either supply a numeric value or remove the key to rely on default ordering.

-weight: 
+# weight: 50            # ← example; adjust to desired position

content/en/docs/applications/redis.md (1)

4-6: Set weight or omit it for consistency

An empty weight: behaves the same as omitting the key but adds noise. Recommend either giving it a concrete number (to control menu order) or deleting the field.

-weight: 
+# weight: 50   # or remove the line entirely

content/en/docs/applications/tenant.md (2)

4-6: Front-matter: avoid weight: without a value

weight: is declared but left empty.
In Hugo this is parsed as null, which:

1. Breaks numeric sorting in menu sections (pages with explicit numbers are grouped first, null sinks to the bottom unpredictably).
2. Yields noisy warnings in strict front-matter linters.

Either assign an explicit integer or drop the key:

-weight: 
+weight: 20            # <- pick an ordering number

If you really want the default ordering, delete the key entirely.

---

2-3: Consider adding a short description: for SEO & search

Most new docs in this PR include a description: field; this one does not.
Adding one keeps front-matter consistent and improves search snippets.

content/en/docs/applications/_include/tenant.md (1)

4-6: Blank weight: value – same issue as main Tenant doc

Leaving weight: empty sets it to null. Use an explicit integer or remove the key to avoid menu-ordering quirks.

-weight: 
+weight: 20   # or delete this line

content/en/docs/applications/_include/nats.md (1)

4-6: Blank weight: – set or drop

Same rationale as previous comments; specify an integer weight or omit the key to keep section ordering deterministic.

-weight: 
+weight: 30   # example

content/en/docs/networking/vpn.md (1)

4-4: Minor duplication in description

The first sentence of the body repeats the exact wording of the description: line.
You might trim one or rephrase to avoid redundancy in search previews.

content/en/docs/applications/_include/rabbitmq.md (1)

4-9: Empty weight and body may lead to an orphaned/blank page

Leaving weight: empty and providing no body means:

1. Hugo will treat the weight as 0, pushing the item to the very top unless overridden elsewhere.
2. The /docs/reference/applications/rabbitmq alias will render a page consisting only of front-matter if the template scripts are not run beforehand.

If the file is always post-processed by hack/update_apps.sh, ignore this. Otherwise, consider either removing weight or giving it an explicit value plus a one-line summary to avoid a blank page.

 weight: 
+summary: "RabbitMQ as a fully-managed Cozystack application."

content/en/docs/applications/_include/postgres.md (1)

4-7: Add a postgresql alias for consistency & SEO

The human-readable name is PostgreSQL, yet the alias uses /postgres.
Add the long form too so old links and search results resolve correctly.

 aliases:
   - /docs/reference/applications/postgres
+  - /docs/reference/applications/postgresql

content/en/docs/networking/http-cache.md (1)

3-7: Alias path may confuse category routing

The page lives under Networking, but the alias points to /reference/applications/http-cache.
Consider also adding a networking-scoped alias for clarity and backlink continuity.

 aliases:
   - /docs/reference/applications/http-cache
+  - /docs/networking/http-cache

content/en/docs/applications/_include/mysql.md (1)

2-6: Weight left empty – define a value or remove the key altogether

weight: is present but has no value. Hugo treats an empty weight as zero, which unintentionally hoists the page to the top of its section.
Either supply an explicit number (keeps ordering predictable) or drop the key.

-weight: 
+# weight: 25        # ← pick an ordering number

content/en/docs/networking/_include/tcp-balancer.md (1)

4-7: Alias path may be misleading – confirm section prefix

The alias points to /docs/reference/applications/tcp-balancer while the file lives under networking.
If the intent is to maintain a legacy URL that lived in “applications”, add a second alias for the new canonical path to avoid 404s.

 aliases:
   - /docs/reference/applications/tcp-balancer
+  - /docs/reference/networking/tcp-balancer   # new canonical location

content/en/docs/virtualization/_include/virtual-machine.md (1)

4-6: Section / alias mismatch – double-check pathing

The alias again references /applications/virtual-machine, yet the document is in the virtualization tree.
Verify that this is intentional (e.g., preserving an old route) and, if not, update accordingly.

-  - /docs/reference/applications/virtual-machine
+  - /docs/reference/virtualization/virtual-machine

content/en/docs/applications/_include/clickhouse.md (1)

4-5: Missing description and weight – fill for consistency & SEO

Other _include files often provide meaningful description text and a numeric weight.
Populate these to keep the autogenerated navigation consistent.

-description: ""
-weight: 
+description: "Managed ClickHouse Service offers a fully-hosted analytics database with zero-ops."
+# weight: 20

content/en/docs/virtualization/virtual-machine.md (1)

4-6: Alias duplicates _include file – OK but ensure no circular canonical link

Adding the same alias here and in _include/virtual-machine.md is harmless, but make sure only one of the two pages is published; otherwise Hugo can emit duplicate URL conflicts.

If _include is merely a shortcode include, everything is fine. If both compile to standalone pages, consider removing the alias from one to avoid clashes.

content/en/docs/kubernetes/_include/_index.md (1)

6-7: Add a trailing slash to the alias to avoid duplicate-URL issues

Hugo treats paths with/without a trailing slash as distinct. Most of the existing docs use the “folder-style” URL (/path/). Appending the trailing slash keeps the alias consistent and prevents accidental 404s or duplicate content penalties.

-  - /docs/reference/applications/kubernetes
+  - /docs/reference/applications/kubernetes/

content/en/docs/virtualization/_include/vm-disk.md (1)

6-6: Align alias with new section location (optional)

If the old path is solely for backward compatibility, consider adding a second alias that reflects the new top-level location (/docs/virtualization/vm-disk/) so both old and new links resolve.

   - /docs/reference/applications/vm-disk
+  - /docs/virtualization/vm-disk/

content/en/docs/virtualization/_include/vm-instance.md (1)

2-7: Alias slug does not match page slug

The file is named vm-instance.md, but the alias is vm-instance while the public title is simply “Virtual Machine”.
For consistency (SEO and user expectations), either:

1. Rename the alias to match the public slug you intend (e.g., /docs/virtualization/virtual-machine/), or
2. Rename the file to virtual-machine.md.

Leaving the mismatch may confuse users and hamper canonical-URL logic.

content/en/docs/networking/_include/http-cache.md (1)

6-7: Consider dual aliases for old and new paths

To ensure legacy links keep working after the doc re-org, you can keep the existing alias and add one for the new networking location:

   - /docs/reference/applications/http-cache
+  - /docs/networking/http-cache/

content/en/docs/networking/_include/vpn.md (1)

4-4: Minor grammar tweak for the description

Current wording misses an article and should pluralise “VPN server”.

-description: "Managed VPN Service simplifies the deployment and management of VPN server, enabling you to establish secure connections with ease."
+description: "Managed VPN Service simplifies the deployment and management of VPN servers, enabling you to establish secure connections with ease."

content/en/docs/guides/platform-stack/_index.md (1)

136-138: Point “Virtual machines” to a populated page instead of the empty section index

/docs/virtualization currently contains only front-matter, so users land on an empty page.
Switch the link to the virtual-machines overview to keep the experience consistent with the earlier Mikrotik/Router guides update.

- -   [Virtual machines]({{% ref "/docs/virtualization" %}}), supporting Linux and Windows OS.
+ -   [Virtual machines]({{% ref "/docs/virtualization/virtual-machines" %}}), supporting Linux and Windows OS.

Makefile (2)

1-12: Add a conventional default all target

Many CI systems & local workflows expect make (with no args) to succeed.
Expose all: that depends on update-all (or another sensible default) to improve ergonomics and satisfy static-analysis warnings.

 .PHONY: all update-apps update-vms update-networking update-k8s update-all \
-        template-apps template-vms template-networking template-k8s template-all
+        template-apps template-vms template-networking template-k8s template-all

+all: update-all

---

12-46: Consider adding a clean target to purge generated files

Static analysis flagged the absence of clean. Having a simple

clean:
	@rm -rf $(APPS_DEST_DIR)/_include \
	         $(VMS_DEST_DIR)/_include \
	         $(NETWORKING_DEST_DIR)/_include \
	         $(K8S_DEST_DIR)/_include

helps local contributors reset stale artefacts.

hack/fill_templates.sh (2)

71-76: Fetch only the first bytes instead of the full README for efficiency

curl -fsSL downloads the whole file even though only the first line is needed.
A --range 0-1023 (or similar) header saves bandwidth and speeds up CI.

-  if ! first_line=$(curl -fsSL "$readme_url" | head -n 1); then
+  if ! first_line=$(curl -fsSL --range 0-1023 "$readme_url" | head -n 1); then

---

83-86: Edge-case: linkTitle may become empty after stripping words

If the README title is exactly “Managed Service”, link_title ends up blank, producing ugly navigation.
Safeguard with a fallback:

- link_title=$(echo "$title" | sed -E 's/\b(Managed|Service)\b//Ig' | xargs)
+ link_title=$(echo "$title" | sed -E 's/\b(Managed|Service)\b//Ig' | xargs)
+ [[ -z "$link_title" ]] && link_title="$title"

hack/update_apps.sh (1)

65-67: SRC_DIR is calculated but never used

The static-analysis warning is correct: SRC_DIR is dead code after refactors.
Drop it to reduce cognitive noise.

-# Derive templates location: DEST_DIR/_include
-SRC_DIR="${DEST_DIR%/}/_include"

content/en/docs/applications/_index.md (2)

55-59: Brand name casing – use “ClickHouse” consistently

Line 58 links to [Clickhouse], but the official spelling is “ClickHouse”.
Consistent casing improves searchability and avoids brand nitpicks.

--   Managed application reference: [Clickhouse]({{% ref "/docs/applications/clickhouse" %}})
+-   Managed application reference: [ClickHouse]({{% ref "/docs/applications/clickhouse" %}})

---

183-185: Replace bare URL with a proper Markdown link

markdownlint flags the naked URL; wrapping it keeps the document lint-clean and improves readability.

--   Docs: https://www.haproxy.com/documentation/
+-   Docs: [HAProxy documentation](https://www.haproxy.com/documentation/)

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

content/en/docs/guides/bundles/_index.md (1)

38-40: Link still lands on an almost-empty placeholder page
Previous feedback recommended pointing the VM link to the “virtual-machines” overview rather than to the section index that currently has no body.
Consider updating the reference to improve reader experience.

-[vm]: {{% ref "/docs/virtualization" %}}
+[vm]: {{% ref "/docs/virtualization/virtual-machines" %}}

hack/update_apps.sh (2)

33-39: Missing value checks for --branch, --apps, and --dest remain unresolved
The script still blindly consumes $2. A dangling flag silently turns the next option into the value.
See prior diff suggestion; re-adding here for convenience.

---

72-85: Destination sub-directories are created only implicitly – cp will fail in CI

cp "$src_file" "$dest_file" expects both parent dirs.
Insert mkdir -p "$(dirname "$src_file")" "$(dirname "$dest_file")" before touch/cp.

Makefile (2)

1-12: Add conventional convenience targets (all, clean, test)
Many CI systems and developers expect these three targets to exist. Even no-op stubs satisfy tooling like checkmake and improve discoverability.

-.PHONY: update-apps update-vms update-networking update-k8s update-all \
-        template-apps template-vms template-networking template-k8s template-all
+.PHONY: all clean test \
+        update-apps update-vms update-networking update-k8s update-all \
+        template-apps template-vms template-networking template-k8s template-all
+
+# Default target – run full update & template generation
+all: update-all template-all
+
+# Place-holders (extend later)
+clean:
+	@echo "Nothing to clean yet"
+
+test:
+	@echo "No tests defined for documentation pipeline"

---

2-5: Minor style nit – align variable columns for readability
K8S, VMS, and NETWORKING lines have uneven spacing compared to the first. Aligning keeps large variable lists easier to scan.

hack/update_apps.sh (1)

65-67: SRC_DIR is computed but never used
Either remove the variable or use it where intended; leaving it unused is a small smell and triggers shellcheck SC2034.

content/en/docs/applications/_index.md (2)

63-64: Hyphenate compound adjectives (“open-source”, “high-performance”)
Consistent technical writing uses hyphens when a compound adjective precedes a noun.

Also applies to: 102-104

---

170-185: Replace bare URL with markdown link for accessibility & lint compliance

-Docs: https://www.haproxy.com/documentation/
+Docs: [HAProxy documentation](https://www.haproxy.com/documentation/)

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro