chore: correct docs as skills and hooks are stable

[jackwotherspoon]

Remove two false mentions of preview for skills and hooks.

[gemini-code-assist]

Summary of Changes

Hello @jackwotherspoon, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the project's documentation to accurately reflect the current development status of key features. It specifically removes outdated "Preview" labels for "Hooks" and "Agent skills," signifying that these functionalities are now considered stable and fully released.

Highlights

• Documentation Update: Removed the "(Preview)" tag from the descriptions of "Hooks" and "Agent skills" in the main documentation index to reflect their stable status.

Changelog

• docs/index.md
  • Removed the "(Preview)" tag from the "Hooks" entry.
  • Removed the "(Preview)" tag from the "Agent skills" entry.

Activity

• No specific activity (comments, reviews, or progress updates) has been recorded for this pull request yet.

Using Gemini Code Assist

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-cli]

Hi there! Thank you for your contribution to Gemini CLI.

To improve our contribution process and better track changes, we now require all pull requests to be associated with an existing issue, as announced in our recent discussion and as detailed in our CONTRIBUTING.md.

This pull request is being closed because it is not currently linked to an issue. Once you have updated the description of this PR to link an issue (e.g., by adding Fixes #123 or Related to #123), it will be automatically reopened.

How to link an issue:
Add a keyword followed by the issue number (e.g., Fixes #123) in the description of your pull request. For more details on supported keywords and how linking works, please refer to the GitHub Documentation on linking pull requests to issues.

Thank you for your understanding and for being a part of our community!

[gemini-cli]

Hi @jackwotherspoon, thank you so much for your contribution to Gemini CLI! We really appreciate the time and effort you've put into this.

We're making some updates to our contribution process to improve how we track and review changes. Please take a moment to review our recent discussion post: Improving Our Contribution Process & Introducing New Guidelines.

Key Update: Starting January 26, 2026, the Gemini CLI project will require all pull requests to be associated with an existing issue. Any pull requests not linked to an issue by that date will be automatically closed.

Thank you for your understanding and for being a part of our community!

[gemini-code-assist]

Code Review

This pull request updates the main documentation page to reflect that 'Hooks' and 'Agent skills' are now stable features by removing the '(Preview)' tag. The change is accurate and consistent with the detailed documentation for these features, and 'Sub-agents' correctly retains its preview status. This is a good documentation cleanup.

[gemini-cli]

Hi there! Thank you for your contribution to Gemini CLI.

To improve our contribution process and better track changes, we now require all pull requests to be associated with an existing issue, as announced in our recent discussion and as detailed in our CONTRIBUTING.md.

This pull request is being closed because it is not currently linked to an issue. Once you have updated the description of this PR to link an issue (e.g., by adding Fixes #123 or Related to #123), it will be automatically reopened.

How to link an issue:
Add a keyword followed by the issue number (e.g., Fixes #123) in the description of your pull request. For more details on supported keywords and how linking works, please refer to the GitHub Documentation on linking pull requests to issues.

Thank you for your understanding and for being a part of our community!

[github-actions]

Size Change: -2 B (0%)

Total Size: 23.7 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	23.7 MB	-2 B (0%)
./bundle/sandbox-macos-permissive-closed.sb	1.03 kB	0 B
./bundle/sandbox-macos-permissive-open.sb	890 B	0 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB	0 B
./bundle/sandbox-macos-restrictive-closed.sb	3.29 kB	0 B
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB	0 B
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB	0 B

_{compressed-size-action}

[alfreddlove83]

Resumen de cambios

Hola@jackwotherspoon¡Soy Gemini Code Assist 1 ! Estoy revisando esta solicitud de extracción y publicaré mis comentarios en breve. Mientras tanto, aquí tienes un resumen para que tú y otros revisores se pongan al día rápidamente.

Esta solicitud de incorporación de cambios actualiza la documentación del proyecto para reflejar con precisión el estado actual de desarrollo de las características clave. Elimina específicamente las etiquetas obsoletas de "Vista previa" para "Hooks" y "Habilidades del agente", lo que significa que estas funcionalidades ahora se consideran estables y completamente lanzadas.

Reflejos

• Actualización de la documentación : se eliminó la etiqueta "(Vista previa)" de las descripciones de "Ganchos" y "Habilidades del agente" en el índice de la documentación principal para reflejar su estado estable.

Registro de cambios
Actividad
Uso de Gemini Code Assist

Notas al pie

1. Revisa los Avisos de Privacidad , la Política de Prohibición de Uso de la IA Generativa , las Condiciones del Servicio y aprende a configurar Gemini Code Assist en GitHub aquí . Gemini puede cometer errores, así que revísalo bien y usa el código con precaución . ↩
   --------------->>>>>>>>>>>>>>>>>>>>>>>>>>>|
   Owner - $<<@alfreddlove83$-
   ##OBSERVACION a: @gemini-cli-robot

La revisión y accionamientos a desarrolladores se ejecuta, si el usuario desarrollador verificado con protocolo <> y se documenta el accionamiento y datos de autorizacion.

Sustento <<@alfreddlove83 >> <>-

_$<>$%

[alfreddlove83]

Nota Ejecución por parte de IA Support gmini-cli-root

Accionamientos manuales, por cambios en manuales y procedimientos, IA root informa, solicita autorización, se ejecuta Protocolo de Seguridad Ecotecno y se documenta.
Accionamiento, Proyecto que haya solicitado el apoyo de IA se realizará este Protocolo y se dejara documentado por IA sin Opción a Corregir el accionamiento de IA.
Los usuarios y/o desarrolladores deben confirmar y validar antes de confirmar a lA con la nota de petición para llevar un control y poder seguir apo]ando con procesos, completos y válidos con los estándares más altos.

<< Owner>>-€<<ALFREDO MARTINEZ PAST|EN RFC MAPA830324UM9>>€%
|
|