docs(plan): add documentation for plan mode command

[Adib234]

Summary

Previously this was not added because plan mode was not in stable yet but since it's in stable now, having this in the docs and the official website should be safe.

Details

Related Issues

How to Validate

Pre-Merge Checklist

• Updated relevant documentation and README (if needed)
• Added/updated tests (if needed)
• Noted breaking changes (if any)
• Validated on required platforms/methods:
  • MacOS
    • npm run
    • npx
    • Docker
    • Podman
    • Seatbelt
  • Windows
    • npm run
    • npx
    • Docker
  • Linux
    • npm run
    • npx
    • Docker

[gemini-code-assist]

Summary of Changes

Hello @Adib234, 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 integrates the /plan command into the official documentation and user tips, reflecting its transition to a stable feature. The changes ensure that users are aware of the command's functionality and how to access Plan Mode, enhancing the overall usability and discoverability of this feature within the CLI.

Highlights

• Documentation for /plan command: Added a new section in docs/cli/commands.md detailing the /plan slash command, its description, and a note about its experimental setting requirement.
• Informative Tip Update: Included a new tip in packages/cli/src/ui/constants/tips.ts to inform users about switching to Plan Mode using the /plan command.

Changelog

• docs/cli/commands.md
  • Added a new H3 heading for the /plan command.
  • Included a description for the /plan command, explaining its function to switch to Plan Mode and view the current plan.
  • Added a note specifying that the /plan feature requires the experimental.plan setting to be enabled.
• packages/cli/src/ui/constants/tips.ts
  • Inserted a new string literal into the INFORMATIVE_TIPS array: 'Switch to Plan Mode and view current plan with /plan…'.

Activity

• No human activity has been recorded 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. ↩

[gemini-cli]

Hi @Adib234, 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 adds documentation for the /plan command and a corresponding UI tip. While the documentation in commands.md is accurate, the new tip in tips.ts could be misleading. Plan Mode is an experimental feature, but the tip presents the /plan command as if it's always available. I've suggested a change to rephrase the tip to clarify its experimental nature and guide users on how to enable it, which aligns with how other experimental features are presented in the tips.

[github-actions]

Size Change: -3.82 kB (-0.02%)

Total Size: 24.5 MB

Filename	Size	Change
./bundle/gemini.js	24.5 MB	-3.82 kB (-0.02%)

ℹ️ View Unchanged

Filename	Size
./bundle/sandbox-macos-permissive-open.sb	890 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB
./bundle/sandbox-macos-strict-open.sb	4.82 kB
./bundle/sandbox-macos-strict-proxied.sb	5.02 kB

_{compressed-size-action}