Skip to content

Add information about the agent skills lifecycle and clarify docs-writer skill metadata.#18234

Merged
g-samroberts merged 4 commits intomainfrom
agent-skills-clarify
Feb 4, 2026
Merged

Add information about the agent skills lifecycle and clarify docs-writer skill metadata.#18234
g-samroberts merged 4 commits intomainfrom
agent-skills-clarify

Conversation

@g-samroberts
Copy link
Contributor

@g-samroberts g-samroberts commented Feb 3, 2026

Summary

Add information about the agent skills lifecycle and clarify docs-writer skill metadata.

Closes #18233

Pre-Merge Checklist

  • [ X] 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

@g-samroberts g-samroberts requested review from a team as code owners February 3, 2026 21:34
@gemini-cli
Copy link
Contributor

gemini-cli bot commented Feb 3, 2026

Hi @g-samroberts, 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-cli
Copy link
Contributor

gemini-cli bot commented Feb 3, 2026

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-code-assist
Copy link
Contributor

Summary of Changes

Hello @g-samroberts, I'm Gemini Code Assist1! 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 enhances the Gemini CLI documentation by providing a comprehensive explanation of the agent skill lifecycle. It clarifies how skills are activated, remain active during specific tasks, and implicitly deactivate upon task completion, thereby improving user understanding of skill management and behavior.

Highlights

  • Agent Skill Lifecycle Documentation: Added a new section detailing the activation, duration, and implicit deactivation of agent skills within the Gemini CLI, providing clarity on their operational lifecycle.
  • Documentation Heading Refinement: Simplified the heading "How it Works (Security & Privacy)" to "How it Works" for improved readability and focus.
Changelog
  • docs/cli/skills.md
    • Renamed the "How it Works (Security & Privacy)" section to "How it Works".
    • Introduced a new subsection "Skill Activation and Deactivation" to describe the process of skill activation, its duration, and implicit deactivation.
Ignored Files
  • Ignored by pattern: .gemini/** (1)
    • .gemini/skills/docs-writer/SKILL.md
Activity
  • The author has marked the "Updated relevant documentation and README (if needed)" item in the pre-merge checklist as complete.
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 gemini-cli bot closed this Feb 3, 2026
@g-samroberts g-samroberts reopened this Feb 3, 2026
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request aims to improve the documentation for agent skills. I've identified a significant issue in the new documentation regarding the skill lifecycle: it incorrectly states that skills are implicitly deactivated. My review of the code indicates that skills remain active for the entire session once enabled. This discrepancy should be corrected to prevent user confusion. Additionally, the changes related to 'docs-writer skill metadata' mentioned in the PR title and description seem to be missing from this pull request.

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

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

@gemini-cli gemini-cli bot added the area/agent Issues related to Core Agent, Tools, Memory, Sub-Agents, Hooks, Agent Quality label Feb 3, 2026
Remove information about deactivation.
@g-samroberts
Copy link
Contributor Author

/gemini review

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request improves the documentation for Agent Skills by clarifying their lifecycle. The heading for the 'How it Works' section has been generalized, and a new 'Skill Activation' section has been added to explain that skills remain active throughout a session once enabled. These changes make the documentation clearer and more comprehensive. The changes are well-implemented and I have no further feedback.

Copy link
Contributor

@jkcinouye jkcinouye left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, one nit

Co-authored-by: Jenna Inouye <jinouye@google.com>
@g-samroberts g-samroberts added this pull request to the merge queue Feb 4, 2026
Merged via the queue into main with commit bd156e6 Feb 4, 2026
26 checks passed
@g-samroberts g-samroberts deleted the agent-skills-clarify branch February 4, 2026 18:06
sidwan02 pushed a commit to sidwan02/gemini-cli-gemma that referenced this pull request Feb 6, 2026
…ter skill metadata. (google-gemini#18234)

Co-authored-by: Jenna Inouye <jinouye@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/agent Issues related to Core Agent, Tools, Memory, Sub-Agents, Hooks, Agent Quality

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add information regarding agent skills lifecycle

2 participants