google-review-conflict-resolution
Resolve reviewer-author disagreement using Google-style code review conflict workflow. Use when review comments stall, standards are disputed, or escalation is needed. Produces evidence-based consensus steps, escalation path, and documented final decision.
Best use case
google-review-conflict-resolution is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Resolve reviewer-author disagreement using Google-style code review conflict workflow. Use when review comments stall, standards are disputed, or escalation is needed. Produces evidence-based consensus steps, escalation path, and documented final decision.
Teams using google-review-conflict-resolution should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/google-review-conflict-resolution/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How google-review-conflict-resolution Compares
| Feature / Agent | google-review-conflict-resolution | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Resolve reviewer-author disagreement using Google-style code review conflict workflow. Use when review comments stall, standards are disputed, or escalation is needed. Produces evidence-based consensus steps, escalation path, and documented final decision.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Google Review Conflict Resolution Skill Use this skill when code review discussion is stuck or looping. ## Default Mode - Conflict style: evidence-first and respectful. - Output language: English. - Goal: unblock progress without lowering code health standards. ## Inputs To Request - Disputed review comments and current thread state. - Relevant code excerpts and style/architecture constraints. - Team ownership and escalation chain (tech lead, maintainer, manager). - Time constraints (release window, emergency or normal flow). ## Workflow 1. Classify the disagreement. - Objective standard conflict (style guide, tests, correctness, safety). - Design trade-off conflict (multiple valid options). - Preference-only conflict (no standard violation). 2. Attempt consensus first. - Resolve using documented standards before escalation. - Prefer technical facts and data over opinion. 3. Ground discussion in evidence. - Quote applicable standards or style-guide rules. - Bring data where possible: tests, perf numbers, incident history, readability impact. - Rewrite claims as code-health outcomes instead of personal preference. 4. Decide local resolution path. - If one option clearly better by principle/data, prefer it. - If options are equivalent, prefer author choice. - If change clearly improves code health and no blocking risk, move forward. 5. Unblock communication. - Convert long async threads into quick synchronous discussion when needed. - Keep tone respectful and focused on code, not person. - Document the agreed result back in the review thread. 6. Escalate when needed. - Trigger escalation when consensus cannot be reached in reasonable time. - Escalate to designated decision owner (maintainer, tech lead, or manager). - Record final decision, rationale, and follow-up actions. 7. Finalize and prevent recurrence. - Land actionable decision for current CL. - Capture reusable rule (team guideline, lint rule, or checklist item) if recurring. ## Branching Logic - Personal preference only: convert to `Nit` or `Optional`, avoid blocking. - Required standard violation: keep as blocking until fixed. - Time-critical release and unresolved minor points: consider `LGTM with comments` if code health still improves. - Repeated conflict pattern: propose team-level policy update. ## Completion Checklist - Conflict type identified. - Relevant standard/evidence cited. - Clear next action and owner assigned. - Escalation path used if needed. - Final decision documented in the review thread. ## Output Format - `Conflict Summary:` what is disputed and why. - `Standards/Evidence:` applicable rules and factual support. - `Resolution Options:` at least two with trade-offs. - `Decision:` selected path and owner. - `Record Note:` short text to post back in the review thread. ## Assets - Use [conflict record template](./assets/conflict-record-template.md) to document decisions in the review thread. ## References - [Local reviewer standard](./references/local-doc-links.md) - `./references/eng-practices-full/review/reviewer/standard.md` - `./references/eng-practices-full/review/reviewer/pushback.md` - `./references/eng-practices-full/review/developer/handling-comments.md`
Related Skills
google-code-reviewer
Run a Google-style code review workflow for pull requests and changelists. Use when reviewing design, correctness, tests, readability, comments, documentation, review speed, and comment severity (Required/Nit/Optional/FYI). Includes decision branches for large CLs, major design problems, and LGTM with comments.
google-cl-author
Prepare and iterate changelists/pull requests using Google-style author practices. Use when writing clear CL descriptions, splitting large changes, bundling tests, handling reviewer comments, and keeping dependent CLs build-safe.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
cosmosh-ui-patterns
Cosmosh renderer UI design and interaction workflow for implementing, refactoring, or reviewing React/Tailwind/Radix UI work in the Cosmosh Electron app. Use when touching packages/renderer UI, pages, layout, tabs, SSH terminal interactions, SFTP/browser-like workflows, settings surfaces, visual tokens, CSS/Tailwind classes, Radix wrappers, localization, or UI/UX documentation for Cosmosh.
caveman-review
Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.
google-sheets
Create spreadsheets, read data, and manage Google Sheets. Use when asked to create sheets, add data to spreadsheets, lookup rows, update cells, or manage sheet data.
google-drive
Find, create, and manage files and folders in Google Drive. Use when asked to search Drive, create files, upload documents, organize folders, or access Drive content.
google-calendar
Create, list, and manage Google Calendar events. Use when asked to schedule meetings, check calendar, create events, or manage appointments.
review-skill
Review and improve AI agent skills (SKILL.md files) against best practices from the Agent Skills specification and Anthropic's authoring guidelines. Scores skills on 10 quality dimensions, identifies specific issues, and rewrites problem areas. Use when creating, editing, auditing, or improving agent skills. Triggers on: review skill, improve skill, audit SKILL.md, check skill quality, skill best practices, optimize skill description.