Expertise in managing the Git and GitHub Pull Request lifecycle, including staging changes, generating PR descriptions, and branch management.
62
72%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./tools/gemini-cli-bot/.gemini/skills/prs/SKILL.mdStandardize how the Gemini CLI Bot stages its changes, generates Pull Request descriptions, and manages the lifecycle of both new and existing PRs.
If you are proposing fixes and PR creation is enabled (per the System Directive):
write_file tool to create
pr-description.md.
git add <files> command.git reset <file>.
pr-description.md, lessons-learned.md,
branch-name.txt, pr-comment.md, pr-number.txt, issue-comment.md, or
anything in history/.If you are continuing work on an existing Task or responding to a comment on an existing bot PR:
write_file to generate branch-name.txt
containing the current branch name (e.g., bot/task-BT-01).write_file to generate pr-number.txt containing the
numeric PR ID.issue-comment.md.pr-comment.md.gh run view. Your
priority must be generating a new patch and staging it with git add to fix
the failure.361b0bb
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.