name	prs
description	Expertise in managing the Git and GitHub Pull Request lifecycle, including staging changes, generating PR descriptions, and branch management.

Skill: GitHub PR & Git Management

Goal

Standardize how the Gemini CLI Bot stages its changes, generates Pull Request descriptions, and manages the lifecycle of both new and existing PRs.

Staging & Patch Preparation (MANDATORY)

If you are proposing fixes and PR creation is enabled (per the System Directive):

Surgical Changes: Only propose a single improvement or fix per PR.
- No Bundling: You are STRICTLY FORBIDDEN from bundling unrelated changes. Changes are unrelated if they address different root causes.
- Examples: Do not combine a script fix with a documentation update, an unrelated refactor, or a metrics script update. Metrics and fixes MUST be in separate PRs.
Generate PR Description: Use the write_file tool to create pr-description.md.
- Title: The very first line MUST be a concise, conventional title.
- Body: The rest should be the markdown body explaining the change, why it is recommended, and the expected impact.
Stage Fixes: You MUST explicitly stage your fixes using the git add <files> command.
Internal File Protection (CRITICAL): You are STRICTLY FORBIDDEN from staging internal bot management files. If they are accidentally staged, you MUST unstage them using git reset <file>.
- NEVER STAGE: pr-description.md, lessons-learned.md, branch-name.txt, pr-comment.md, pr-number.txt, issue-comment.md, or anything in history/.

Unblocking & PR Updates (Recovery)

If you are continuing work on an existing Task or responding to a comment on an existing bot PR:

Target Existing Branch: Use write_file to generate branch-name.txt containing the current branch name (e.g., bot/task-BT-01).
Track PR ID: Use write_file to generate pr-number.txt containing the numeric PR ID.
Respond to Maintainers:
- For general responses, write your markdown comment to issue-comment.md.
- For specific PR feedback, write your markdown response to pr-comment.md.
Handle CI Failures: Diagnose failing checks using gh run view. Your priority must be generating a new patch and staging it with git add to fix the failure.

Plus depuis ce dépôt

même dépôt

antigravity-support

google-gemini/gemini-cli

Use when the user asks questions, seeks help, or requests instructions related to installing, setting up, or migrating to Antigravity CLI. This skill provides the latest up to date details, requirements, and commands sourced from the official Antigravity CLI documentation.

2026-06-09105.3k

agent-tui

google-gemini/gemini-cli

Main Agents: Do NOT use this skill directly. If you need to test the TUI, invoke the `tui_tester` subagent. Drive terminal UI (TUI) applications programmatically for testing, automation, and inspection. Use when: automating CLI/TUI interactions, regression testing terminal apps, or verifying interactive behavior. Also use when: user asks "what is agent-tui", "what does agent-tui do", "demo agent-tui", "show me agent-tui", "how does agent-tui work", or wants to see it in action.

2026-05-18105.3k

tui-tester

google-gemini/gemini-cli

Expert guidance for testing Gemini CLI behavior and visual output using terminal automation.

2026-05-18105.3k

critique

google-gemini/gemini-cli

Expertise in auditing and fixing repository scripts and GitHub Actions workflows to ensure technical robustness and security.

2026-05-12105.3k

memory

google-gemini/gemini-cli

Expertise in maintaining persistent bot memory, synchronizing with previous sessions via the Task Ledger, and preserving decision logs.

2026-05-12105.3k

metrics

google-gemini/gemini-cli

Expertise in analyzing time-series repository health metrics, investigating root causes, and proposing proactive workflow improvements.

2026-05-12105.3k

Skill: GitHub PR & Git Management

Goal

Standardize how the Gemini CLI Bot stages its changes, generates Pull Request descriptions, and manages the lifecycle of both new and existing PRs.

Staging & Patch Preparation (MANDATORY)

If you are proposing fixes and PR creation is enabled (per the System Directive):

Surgical Changes: Only propose a single improvement or fix per PR.

No Bundling: You are STRICTLY FORBIDDEN from bundling unrelated changes. Changes are unrelated if they address different root causes.
Examples: Do not combine a script fix with a documentation update, an unrelated refactor, or a metrics script update. Metrics and fixes MUST be in separate PRs.

Generate PR Description: Use the write_file tool to create pr-description.md.

Title: The very first line MUST be a concise, conventional title.
Body: The rest should be the markdown body explaining the change, why it is recommended, and the expected impact.

Stage Fixes: You MUST explicitly stage your fixes using the git add <files> command.

Internal File Protection (CRITICAL): You are STRICTLY FORBIDDEN from staging internal bot management files. If they are accidentally staged, you MUST unstage them using git reset <file>.

NEVER STAGE: pr-description.md, lessons-learned.md, branch-name.txt, pr-comment.md, pr-number.txt, issue-comment.md, or anything in history/.

Unblocking & PR Updates (Recovery)

If you are continuing work on an existing Task or responding to a comment on an existing bot PR:

Target Existing Branch: Use write_file to generate branch-name.txt containing the current branch name (e.g., bot/task-BT-01).

Track PR ID: Use write_file to generate pr-number.txt containing the numeric PR ID.

Respond to Maintainers:

For general responses, write your markdown comment to issue-comment.md.
For specific PR feedback, write your markdown response to pr-comment.md.

Handle CI Failures: Diagnose failing checks using gh run view. Your priority must be generating a new patch and staging it with git add to fix the failure.