MediaMetz/gemini-cli
1
0
Fork 0
mirror of https://github.com/google-gemini/gemini-cli.git synced 2026-05-27 20:22:58 -07:00
Code Issues Packages Projects Releases Wiki Activity

fix(bot): mandate internal skill activation and workspace root writes in task skills

Browse Source
This commit is contained in:
Christian Gunderman
2026-05-14 12:05:47 -07:00
parent ad612d9311
commit 67b46ee365
2 changed files with 10 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tools/gemini-cli-bot/.gemini/skills/issue-fixer/SKILL.md
+4 -2
View File
@@ -22,7 +22,9 @@ maintain existing PRs to reduce the repository backlog.
## Workflow
1. **Inventory & Drive PRs**: Use the `prs` skill to list all open PRs labeled `bot-fix`.
1. **Inventory & Drive PRs**:
- **ACTIVATE SKILLS**: You MUST call `activate_skill(name="memory")` and `activate_skill(name="prs")` before continuing.
- Use the `prs` skill to list all open PRs labeled `bot-fix`.
- If any require attention (CI failure, requested changes), focus your entire run on resolving ONE of them.
- Do NOT start a new issue fix if an existing PR needs work.
2. **Search for Candidates**: If no PRs need attention, search for `effort/small` issues: `gh issue list --label "effort/small" --limit 10 --json number,title,url`.
@@ -30,4 +32,4 @@ maintain existing PRs to reduce the repository backlog.
3. **Select ONE Issue** and implement a fix on a new branch.
- **Efficient Searching**: When searching the codebase with `grep_search`, you MUST search one top-level folder at a time (e.g. `packages/core`, `packages/cli`) to avoid timeouts. Avoid searching problematic directories with large data files like `memory-tests` and `last_brain_data` unless absolutely necessary.
4. **Verify**: You MUST run `timeout 10m npm run preflight` to verify. Wrapping test commands in `timeout` is mandatory to prevent hanging the CI environment if your changes introduce an infinite loop.
5. **Use the `prs` Skill** to stage changes and prepare the draft PR (labels: `bot-fix`, `issue-fixer`).
5. **Use the `prs` Skill** to stage changes and prepare the draft PR (labels: `bot-fix`, `issue-fixer`). Ensure you write `pr-description.md` and `pr-labels.txt` to the **workspace root**.
tools/gemini-cli-bot/.gemini/skills/metrics/SKILL.md
+6 -1
View File
@@ -20,7 +20,12 @@ maintainability.
- Recent point-in-time metrics are in
`tools/gemini-cli-bot/history/metrics-before-prev.csv` and the current run's
metrics.
- **Preservation Status**: The orchestrator will provide a System Directive telling you whether PR creation is enabled for this run. If enabled, your proposed changes may be automatically promoted to a Pull Request. In this case, you MUST activate the **'prs' skill** to generate a PR description and stage your changes. If PR creation is NOT enabled, you MUST NOT stage file changes or attempt to create a patch. Instead, simply report your findings.
## Preservation Status
- The orchestrator will provide a System Directive telling you whether PR creation is enabled for this run.
- **ACTIVATE SKILLS**: You MUST call `activate_skill(name="memory")` at the start of your investigation.
- **PR Skill**: If PR creation is enabled, you MUST call `activate_skill(name="prs")` to generate a PR description and stage your changes. You MUST write `pr-description.md` and `pr-labels.txt` to the **workspace root**.
- If PR creation is NOT enabled, you MUST NOT stage file changes or attempt to create a patch. Instead, simply report your findings.
- **Ownership Mandate**: Any PR generated by this skill MUST use the `bot-fix` and `metrics` labels in `pr-labels.txt`.
## Repo Policy Priorities