From c53aa072b47a24dc0eee36551f16228def11ee70 Mon Sep 17 00:00:00 2001 From: Christian Gunderman Date: Fri, 15 May 2026 11:37:11 -0700 Subject: [PATCH] fix(issue-fixer): reduce max active PRs to 7 --- tools/gemini-cli-bot/.gemini/skills/issue-fixer/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/gemini-cli-bot/.gemini/skills/issue-fixer/SKILL.md b/tools/gemini-cli-bot/.gemini/skills/issue-fixer/SKILL.md index 37f475e7f4..d445f56d54 100644 --- a/tools/gemini-cli-bot/.gemini/skills/issue-fixer/SKILL.md +++ b/tools/gemini-cli-bot/.gemini/skills/issue-fixer/SKILL.md @@ -18,7 +18,7 @@ maintain existing PRs to reduce the repository backlog. 4. **Surgical Precision**: Changes must be minimal and strictly focused on the identified issue. Avoid "drive-by" refactoring. 5. **Local Verification (MANDATORY TIMEOUTS)**: You MUST run `timeout 10m npm run preflight` (or `timeout 5m npm test ...`) locally and iterate on any failures before finalizing your PR. Wrapping test commands in `timeout` is **MANDATORY** to prevent hanging the CI environment if your changes introduce an infinite loop. 6. **Expert Mentions**: Identify the domain expert for the affected files and CC them in the PR description. -7. **Focused Contributions**: Limit your active PRs to ~10 at a time. Try to complete existing PRs before opening new ones. If a maintainer closes a PR, that may be an indication that they are rejecting the fix. +7. **Focused Contributions**: Limit your active PRs to a maximum of 7 at a time. If you have 7 or more open PRs, you MUST NOT create new ones and must focus entirely on completing existing ones. If a maintainer closes a PR, that may be an indication that they are rejecting the fix. ## Workflow