Pulls
Open and improve PRs; status/checks; hand off to merge-it when needed.
What it is
Section titled “What it is”Open and improve PRs; status/checks; hand off to merge-it when needed. This practice is a skill-mapped TTP: when, why, and which command—not a full copy of the skill. Open the skill to execute.
Why it works
Section titled “Why it works”Pull requests are the modern code-review batch. Google’s eng practices favor small, reviewable changes; GitHub PRs plus required checks make review and CI the integrate gate for trunk-based teams.
When to use it
Section titled “When to use it”When the situation matches the one-liner above and Orientation (or your project path) says this is the fire to touch now.
- Invoke the skill; follow its safety rules
- Keep one write owner; collect evidence before claiming done
- With only a PR identifier (± details), or no-arg on a current-branch PR, execute completion work — don’t menu admin commands
- After explicit admin shaping, offer to execute landing (
merge-it,fix-it,check-readiness,stage-it/ship-it) - Hand off to the next practice instead of boiling the ocean
- Skip orientation when you’re lost
- Spawn overlapping agents to “go faster”
- Treat the practice as done without evidence
Related concepts
Section titled “Related concepts”06-work-ownership, 04-evidence-over-vibes
Further reading
Section titled “Further reading”See also the handbook Sources & grounding bibliography.
Agent skill
Section titled “Agent skill”pulls