submit-suggestion

Submit GKE configuration changes via GitHub Pull Requests.

42|32|Updated May 7, 2026
One-click install
npx skills add https://github.com/gke-labs/kube-agents --skill submit-suggestion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: submit-suggestion
Source: https://github.com/gke-labs/kube-agents/tree/main/agents/platform/skills/submit-suggestion
Command: npx skills add https://github.com/gke-labs/kube-agents --skill submit-suggestion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, and includes scripts (resource) components.

What problem does it solve?

This skill eliminates the risk of manual, error-prone infrastructure mutations by enforcing a secure, GitOps-based workflow for all configuration changes.

Core Features & Use Cases

  • Secure GitOps Orchestration: Automates branch creation, file staging, and Pull Request submission using GitHub App tokens.
  • Governance Enforcement: Ensures all infrastructure changes undergo human review and follow Conventional Commit standards.
  • Use Case: When the Platform Agent needs to update a GKE network policy, it uses this skill to commit the change to a feature branch and open a PR, ensuring the change is audited and approved before deployment.

Quick Start

Use the submit-suggestion skill to propose a new GKE manifest update by creating a branch and submitting a pull request for the specified configuration change.

Frequently Asked Questions about submit-suggestion

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

FAQPage Schema
How do I automate infrastructure pull requests for GKE configuration updates?

To automate GitOps pull requests for GKE, the skill orchestrates branch creation, commits staged configuration files, and submits a PR using authenticated GitHub App tokens, ensuring all infrastructure changes undergo human review.

What is the best way to enforce governance for GitOps infrastructure mutations?

Enforcing governance for GitOps infrastructure mutations requires routing all changes through automated pull request workflows. This ensures manual errors are eliminated by mandating human review and Conventional Commit standards for every configuration update.

Do I need GitHub CLI and local repository access to automate GitOps PR submission?

Yes, automating GitOps PR submission requires the GitHub CLI and local repository access. These dependencies are necessary to perform authenticated Git operations and execute token-based PR creation for your infrastructure changes.

Can I use this approach to update GKE network policies without manual Git operations?

Yes, you can update GKE network policies without manual Git operations by using an automated agent to commit changes to a feature branch and open a PR. This ensures the configuration update is securely audited and approved before deployment.

How does branch management work for automated declarative configuration updates?

Branch management for automated declarative configuration updates works by creating a dedicated feature branch, staging the modified files, and submitting a pull request. This isolated workflow guarantees changes are reviewed before merging into the main branch.

Does automated PR orchestration support Conventional Commit standards for Kubernetes manifests?

Yes, automated PR orchestration supports Conventional Commit standards for Kubernetes manifests. It enforces these governance policies during the commit staging and pull request submission process to maintain consistent infrastructure change history.