oncall
Skill561 starsChanged 17 days agoApache-2.0View on GitHub
Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).
- Commits and pushes
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- pw_ghish/AGENTS.mdAGENTS.md
- pw_ide/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- BluetoothSkill
- Code ReviewSkill
- crankSkill
- docsSkill
- freshenSkill
- ghishSkill
- manual-cli-testSkill
- pw_async2Skill
- Pigweed Kernel TestingSkill
- C++ Pigweed RPC ServicesSkill
- respondSkill
- reviewSkill
- run-presubmit-checksSkill
- saleae-analyzerSkill
- Use Pigweed Toolchain ToolsSkill
- Multi-Agent Worktree & Bazel Cache ManagementSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
/oncall presubmit: Run presubmit verification on your branch or stack. - Very specific: line 55
Do not use the mutable latest ref in .cipd_version (it causes selfupdate validation failures).
- Very specific: line 57
Always ensure all platform digests in .cipd_version.digests are generated and verified.
- Distinctive: line 64
Run the oncall helper script:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pigweed Oncall Workflows
This skill provides operational workflows and runbooks for the Pigweed oncall rotation. It is designed to be manually triggered via slash commands to prevent unnecessary auto-loading.
Invoking this Skill
Trigger this skill and its subskills explicitly using slash commands in the prompt:
/oncall: Access the general oncall workflow, overview, and task router./oncall roll-cipdor/roll-cipd: Trigger the CIPD client update subskill (b/315378787), which rolls the pin, creates apw_env_setup: Roll cipdcommit, and submits it./oncall presubmit: Run presubmit verification on your branch or stack.
Oncall Responsibilities & Subskills
| Subskill / Command | Description | Runbook / Tool |
/roll-cipd | Update pinned CIPD version, create pw_env_setup: Roll cipd commit, and submit to Gerrit (b/315378787) | roll_cipd.md / roll_cipd.py |
/oncall presubmit | Run presubmit checks across commit stacks | Run Presubmit Checks |
/oncall review | Review incoming and ongoing Git/Gerrit patches | Code Review |
Subskill: Roll CIPD Client (b/315378787)
CIPD (Chrome Infra Package Deployer) is used by Pigweed to install and manage prebuilt toolchains and binaries. Updating the CIPD client pin is a recurring oncall maintenance task tracked under b/315378787.
Triggers
- Explicit user slash commands:
/roll-cipdor/oncall roll-cipd. - Explicit user prompt during oncall rotation specifically requesting CIPD pin roll.
Guards
- Do not auto-load on general tool, environment, or setup tasks unless explicitly requested.
- Do not use the mutable
latestref in.cipd_version(it causes selfupdate validation failures). - Always ensure all platform digests in
.cipd_version.digestsare generated and verified.
Execution Workflow
Option 1: Automated Roll, Commit & Push (Recommended)
Run the oncall helper script:
# Roll and commit
python3 .agents/skills/oncall/scripts/roll_cipd.py --commit
# Roll, commit, and submit to Gerrit
python3 .agents/skills/oncall/scripts/roll_cipd.py --commit --pushOption 2: Manual Roll, Commit & Push
- Determine candidate
git_revisiontags:python3 pw_env_setup/py/pw_env_setup/cipd_setup/wrapper.py describe \ infra/tools/cipd/linux-amd64 -version latest - Roll version and update digests:
python3 pw_env_setup/py/pw_env_setup/cipd_setup/wrapper.py selfupdate-roll \ -version-file pw_env_setup/py/pw_env_setup/cipd_setup/.cipd_version \ -version git_revision:<HASH> - Check and verify:
python3 pw_env_setup/py/pw_env_setup/cipd_setup/wrapper.py selfupdate-roll \ -version-file pw_env_setup/py/pw_env_setup/cipd_setup/.cipd_version \ -check - Verify client functionality:
python3 pw_env_setup/py/pw_env_setup/cipd_setup/wrapper.py -version - Commit changes:
git add pw_env_setup/py/pw_env_setup/cipd_setup/.cipd_version \ pw_env_setup/py/pw_env_setup/cipd_setup/.cipd_version.digests git commit -m "$(cat <<'EOF'
pw_env_setup: Roll cipd
Rolls CIPD client version to <git_revision>.
Bug: 315378787 EOF )"
6. Submit to Gerrit:
```bash
./gh pr create --cqFor full details and troubleshooting, see the roll_cipd.md runbook.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

