feat: Add docs maintainer and Celestia router skills

[jcstein]

Overview

[gemini-code-assist]

Summary of Changes

Hello @jcstein, 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 introduces two new "skill" definitions to streamline development and documentation processes within the Celestia project. One skill provides detailed guidelines for maintaining the Celestia documentation site, ensuring consistency and accuracy. The other establishes a routing mechanism to direct broad Celestia tasks to the appropriate repository, clarifying ownership and preventing misdirected effort.

Highlights

• Docs Maintainer Skill: Introduced a comprehensive guide for maintaining Celestia documentation, covering structural rules, style guidelines, variable usage, directory intent, chain-id warnings, link rules, repository facts, and a workflow checklist.
• Celestia Router Skill: Added a skill definition for routing Celestia-related tasks to the correct repositories (docs, celestia-app, celestia-node, cips), including decision rules, an intake checklist, handoff behavior, and safety considerations.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• SKILL.md
  • Added a new skill definition for Celestia documentation maintenance.
• skills/celestia-router/SKILL.md
  • Added a new skill definition for routing Celestia tasks across repositories.

Activity

• No activity has occurred on 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. ↩

[github-actions]

🚀 Preview Deployment

Your preview is ready: https://celestiaorg.github.io/docs-preview/pr-2427/

[gemini-code-assist]

Code Review

This pull request introduces two new "skill" definition files, celestia-docs-maintainer and celestia-router, which provide instructions for an automated agent. The changes are clear and well-structured. My main feedback concerns some inconsistencies in network naming conventions across the new files and with existing documentation, and a minor markdown formatting issue. Additionally, for better organization, you might consider placing the celestia-docs-maintainer skill file within the skills/ directory, similar to the router skill.

[gemini-code-assist]

There are some inconsistencies in the network names used here compared to other parts of the documentation and even within this file. For example:

• Line 20 mentions Mocha, but it's missing from this example list.
• Other documentation files (e.g., app/operate/networks/overview/page.mdx) refer to networks as Mocha testnet and Arabica devnet.

To ensure clarity and consistency, it would be beneficial to use the canonical network names and make this list of examples more complete. For instance, you might want to add an example for Mocha testnet and clarify if Arabica from line 20 should be Arabica devnet as used here.

[gemini-code-assist]

The list of network scopes here (Coffee Beta, Mocha, Arabica, or mainnet) appears to be inconsistent with the names used elsewhere in the documentation (e.g., Mainnet Beta, Mocha testnet, Arabica devnet). To improve clarity and prevent confusion when routing tasks, consider aligning these names with the canonical network names used across the project.