skills.rest
missBerg
missBergCOMMUNITY
Explore all skills by this author →
GitHub

eg-contrib-pr-guide

Documents conventions for submitting pull requests to envoyproxy/gateway.

3|Updated Mar 8, 2026
Search Tags:#git#contributing#code-review#pull-request#envoy-gateway#pr-guide
One-click install
npx skills add https://github.com/missBerg/envoy-skills --skill eg-contrib-pr-guide
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eg-contrib-pr-guide
Source: https://github.com/missBerg/envoy-skills/tree/main/gateway/contributors/skills/eg-contrib-pr-guide
Command: npx skills add https://github.com/missBerg/envoy-skills --skill eg-contrib-pr-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This PR guide helps contributors follow consistent PR conventions, making reviews faster and more predictable, and reducing back-and-forth due to formatting ambiguities.

Core Features & Use Cases

  • PR Title Format: type(subsystem): short, lowercase description to improve traceability.
  • Commit Message Conventions: standardized messages that mirror the PR type and scope.
  • Review Expectations: defined turnaround times, required approvals, and coding standards, with examples.

Quick Start

Review this guide before opening your first PR to envoyproxy/gateway.

Frequently Asked Questions about eg-contrib-pr-guide

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

FAQPage Schema
How do I format a pull request for Envoy Gateway contributions?▼

Format Envoy Gateway pull requests using the convention type(subsystem): short, lowercase description. This standardized PR title format improves traceability and ensures your contribution aligns with project conventions before review.

What commit message conventions are required for envoyproxy/gateway?▼

Commit message conventions for envoyproxy/gateway require standardized messages that mirror the PR type and scope. This consistency makes reviews faster and more predictable by reducing formatting ambiguities across contributions.

Do I need DCO sign-off for Envoy Gateway pull requests?▼

Yes, DCO sign-off is required for Envoy Gateway pull requests. The contribution guide enforces structured guidelines including Developer Certificate of Origin sign-off to maintain collaborative code review standards.

What are the code review expectations for Envoy Gateway contributions?▼

Code review expectations for Envoy Gateway include defined turnaround times, required approvals, and adherence to coding standards. These guidelines streamline the review process and improve collaboration across the gateway project.

Can I use this PR guide for contributing to any git repository?▼

No, this PR guide specifically streamlines PR conventions, commit formatting, and review expectations for envoyproxy/gateway contributions. The subsystem scoping, types, and documentation practices are tailored to the Envoy Gateway project.

How do I include documentation updates in an Envoy Gateway PR?▼

Include documentation updates in your Envoy Gateway PR by following the enforced documentation practices outlined in the contribution guide. This ensures your pull request meets the collaborative standards required for approval.

Related Skills

Explore More Software Engineering Skills→
hengsinhengsin
20

idempiere-setup

Provision a complete iDempiere development environment with Eclipse, Maven, and database configuration.

Community
Advanced
NVIDIANVIDIA
22.1k

nemoclaw-contributor-create-pr

Automates GitHub pull request creation with enforced prerequisites and NemoClaw's PR template via gh CLI.

Official
Advanced
bennybennisonbennybennison

verification-loop

Run sequential build, type, lint, test, security, and diff checks.

Community
Intermediate
michaelvolzmichaelvolz

rm-commit

Create repo-specific conventional commit payloads from the working tree.

Community
Intermediate