[kikoso]

Makes the agent setup tool-neutral, adds pull request rules that came up repeatedly in recent reviews, and adds a CI check for leftovers of local or agent-assisted work.

Tool-neutral setup

• The skill moves from .gemini/skills/ to .agents/skills/. .claude/skills and .gemini/skills are symlinks to it, so Claude Code, Gemini CLI and Codex all find the same skill.
• GEMINI.md imports AGENTS.md, like CLAUDE.md already does.
• Every reference to the old path moves with it: release-please-config.json, release-rc.yml, update_skill.py and answer_issue.py. release-please and the RC workflow edit the real file, not a symlink.
• .gemini/config.yaml and .gemini/styleguide.md stay where they are, since they configure Gemini Code Assist reviews.

AGENTS.md

• New "Agent setup" section describing the layout above.
• Pull request rules: keep a PR to what its title says (and fix the type if the scope changes), answer every review thread before asking for another review, and never commit local paths, internal links, bug IDs or API keys.

Agent leftovers check

.github/workflows/agent-leftovers.yml runs .github/scripts/check_agent_leftovers.py on every pull request. It scans only what the PR adds (added lines, new file names, commit messages, title and body) for:

• local paths and file:// URLs into home or temp directories
• go/ links, b/ bug IDs, corp and googleplex hosts
• Google API keys
• AI co-author trailers and links to agent chat sessions
• local agent settings files and .orig/.rej merge leftovers

A line can opt out with agent-leftovers: ignore. Findings show as annotations on the PR.

Tested against the last 250 commits on main of this repo, android-maps-utils and android-places-compose: it flags two real cases (agent session links in commit messages) and no false positives, plus a synthetic commit that triggers every pattern.

Notes

• update_skill.py gets a one-line path change, so it will conflict trivially with fix(ci): update Gemini model and harden update-skill against prompt injection #991, which fixes the failing Update Skill workflow. Whichever merges second needs a small rebase.
• This touches .github/, so it needs a googlemaps-admin approval.

[github-actions]

Coverage (unit tests)

Compared against 3f9353b on main (#1043).

Module	Line %	Change	Branch %	Change
maps-compose	15.28%	no change	3.76%	no change
maps-compose-utils	6.09%	no change	4.47%	no change
maps-compose-widgets	0.00%	no change	0.00%	no change
TOTAL	12.41%	no change	3.79%	no change

_{Line and branch coverage from unit test reports. History is recorded on the coverage-history branch after each merge to main.}

[googlemaps-bot]

Coverage (instrumentation tests)

Overall Project	43.54%	🍏

There is no coverage information present for the Files changed