사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/google-gemini/gemini-cli --skill prs시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
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_filetool 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_fileto generatebranch-name.txt
containing the current branch name (e.g., bot/task-BT-01).
- Track PR ID: Use
write_fileto generatepr-number.txtcontaining 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.
