google-cl-author

Generate CL plans, description drafts, test plans, and review response plans.

7|1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/agoudbg/Cosmosh --skill google-cl-author
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: google-cl-author
Source: https://github.com/agoudbg/Cosmosh/tree/main/.agents/skills/google-cl-author
Command: npx skills add https://github.com/agoudbg/Cosmosh --skill google-cl-author

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Many changelists and pull requests lack clear, reviewable descriptions, sensible scope, and an actionable test and response plan, which slows reviews and increases rework. This Skill helps authors distill changes, split large CLs safely, and craft descriptions and responses that make reviews faster and more effective.

Core Features & Use Cases

  • CL sizing & splitting: Recommend how to split a large change by dependency stack, files, horizontal/vertical layers, or feature cells so each CL stays reviewable and build-safe.
  • Description drafting & templates: Produce a first-line imperative summary and a contextual body explaining what changed, why, trade-offs, validation, and links using the provided CL description template.
  • Test and review response planning: Generate a concise Test Plan and classified Review Response Plan (required changes, nits, optional) and final submission checklist to keep builds healthy.
  • Use Case: Turn a mixed refactor+feature diff into a prioritized series of small CLs with a draft description, tests to add, and scripted responses for expected reviewer comments.

Quick Start

Prepare a CL Plan, Description Draft, Test Plan, and Review Response Plan for this change: summarize the change, state the approximate size (LOC/files), list tests status, and paste any open reviewer comments.

Frequently Asked Questions about google-cl-author

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a reviewable pull request description for a large change?

Splitting a large changelist for code review involves recommending divisions by dependency stack, files, horizontal or vertical layers, or feature cells so each CL remains reviewable and build-safe.

What is the best way to split a large changelist for code review?

Splitting a large changelist for code review involves recommending divisions by dependency stack, files, horizontal or vertical layers, or feature cells so each CL remains reviewable and build-safe.

How do I plan tests and respond to reviewer comments on a pull request?

To plan tests and respond to reviewer comments on a pull request, generate a concise Test Plan and a classified Review Response Plan that separates required changes, nits, and optional suggestions to keep builds healthy.

What information do I need to draft a focused CL and test plan?

To draft a focused CL and test plan, you need to provide a change summary, approximate CL size in lines of code or files, test status, dependency chain, and any open reviewer feedback to produce the plan.

Can I use Google-style authoring practices to turn a mixed refactor and feature diff into smaller CLs?

You can use Google-style authoring practices to turn a mixed refactor and feature diff into a prioritized series of small CLs, complete with a draft description, tests to add, and scripted responses for expected reviewer comments.