// Use for ALL documentation-related workflows: rst style guide, changelog updates, C/C++ API reference (Doxygen)
>-
Run toolchain binaries (objdump, nm, size, readelf, strip, etc) to disassemble code, list symbols, analyze binary size, and inspect ELF artifacts. MUST be used instead of system tools.
Guide to defining, implementing, and testing a new Pigweed RPC service in C++ using Nanopb, pw_protobuf, or raw methods.
Instructions for running tests and lints for the Pigweed kernel (`pw_kernel`).
Comprehensive workflow for reviewing Git patches and Gerrit Change Lists (CLs).
Instructions for working with Bluetooth code (pw_bluetooth_sapphire, pw_bluetooth_proxy, etc.) and the Bluetooth Core Specification.
| name | docs |
| description | Use for ALL documentation-related workflows: rst style guide, changelog updates, C/C++ API reference (Doxygen) |
Pigweed has many docs automation workflows. Rather than list them all here, this skill helps agents decide which workflows are relevant and then routes them to the full instructions.
Summarize the user's main goal in a few sentences.
If the user's main goal is not docs-related and there is still work to be done, STOP HERE.
[!WARNING]
The docs workflows may reduce your ability to solve the user's main goal because they create high risk of context pollution.
Examples of WIP main goals unrelated to docs:
Run ALL workflows that are relevant to the user's main goal.
Each of the sections below represents a workflow. Summary:
All workflows follow this pattern:
Triggers: Hints about when to run the workflow. Values in double quotes
represent example prompts.Guards: Warnings about when to NOT run the workflow.Path: The path to the full instructions.Triggers:
*.rst files are in context.Guards:
Path: //docs/agents/rst/AGENTS.md
Triggers:
Guards:
Path: //docs/agents/changelog/AGENTS.md
Triggers:
//docs/doxygen has failed to buildGuards:
Path: //docs/agents/doxygen/AGENTS.md