eng-practices

Generate role-aware code-review guidance from Google Eng Practices.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/sunzhk/shared-skills --skill eng-practices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eng-practices
Source: https://github.com/sunzhk/shared-skills/tree/main/eng-practices
Command: npx skills add https://github.com/sunzhk/shared-skills --skill eng-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates Google Eng Practices into actionable, role-aware code-review guidance to streamline reviewer and author interactions and improve outcomes.

Core Features & Use Cases

  • Provides a unified review checklist, role-specific actions, and emergency-review handling.
  • Supports breaking large changes into Small CLs and efficient rollback strategies.
  • Suitable for daily team reviews, cross-team collaboration, and strict-compliance review scenarios.

Quick Start

Apply the eng-practices core review process to a pending PR/CL and generate actionable, role-aware guidance.

Frequently Asked Questions about eng-practices

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

FAQPage Schema
How do I automate code review guidance for pull requests?

Automate code review guidance by applying Google Eng Practices to pending pull requests to generate actionable, role-aware instructions for reviewers and authors, streamlining interactions and improving outcomes.

What is the best way to break large pull requests into small CLs?

Breaking large changes into Small CLs requires structured decomposition strategies to simplify reviews and enable efficient rollback. This approach aligns changes with review checklists to加速 code reviews to higher quality.

Can I get role-specific actions for reviewers and authors during code reviews?

Yes, role-specific actions for reviewers and authors are provided through a unified review checklist. This handles reviewer and author interactions, ensuring deterministic execution of review steps and proper conflict handling across teams.

How do I handle review conflicts across teams during code review?

Handle review conflicts across teams using deterministic execution of review steps and role-aware guidance based on Google Eng Practices. This ensures cross-team collaboration scenarios maintain strict compliance and clear conflict resolution.

Does this work for strict-compliance code review scenarios?

Yes, this applies to strict-compliance review scenarios by providing a unified review checklist and deterministic execution of review steps. It satisfies requirements for role-aware guidance and emergency-review handling.