How Issues Are Managed in the Google Skills Project: A Complete Guide

The Google Skills project uses GitHub Issues as its exclusive channel for bug reports, feature requests, and skill suggestions, with external contributions accepted only through issue filing rather than pull requests.

The google/skills repository is an internal Google project that publishes skill definitions and examples for developer tools. Because the codebase is maintained entirely by internal teams, the project follows a strict issue-centric workflow that directs all community feedback through GitHub's issue tracker. This article explains exactly how that workflow operates, where to file issues, and what happens after submission.

Where to File Issues in google/skills

All issues for the Google Skills project are tracked at https://github.com/google/skills/issues. This is the sole official channel for reporting problems or requesting new capabilities.

According to the README.md at lines 70-73, users should "search for existing issues or open a new one" when they encounter problems or have suggestions ¹. The repository does not use external ticketing systems, email lists, or discussion forums for issue management.

The No-Pull-Request Contribution Policy

A critical aspect of issue management in this project is that external pull requests are not accepted. The CONTRIBUTING.md file explicitly states this policy at lines 17-23 ²:

The team does not accept external pull requests. Instead, they ask contributors to report issues or request new skills via the issue tracker.

This policy means:

• Bug fixes must be reported as issues for internal teams to implement
• New skill requests require an issue describing the desired functionality
• Documentation corrections follow the same issue-only path
• Security concerns are handled through private issue reporting or Google's security disclosure process

The Issue Lifecycle: From Filing to Resolution

The Google Skills issue workflow follows four stages:

1. Problem identification — A user discovers a bug, outdated SDK pattern, security anti-pattern, or skill gap
2. Issue creation — The user opens a GitHub issue with appropriate labels and description
3. Internal triage — Google team members review, label, prioritize, and assign the issue
4. Resolution communication — Updates, fixes, and closure notices post to the issue thread

Internal teams use labels to categorize issues by type (bug, enhancement, security, documentation) and priority. Resolution status is always visible in the public issue thread.

How to Create a Google Skills Issue

Using the GitHub Web Interface

Navigate to https://github.com/google/skills/issues and click "New issue." Select the appropriate template if available, or use the blank issue format.

Using the GitHub CLI

For command-line users, the gh tool streamlines issue creation:

gh issue create \
  --repo google/skills \
  --title "Bug: Outdated example in BigQuery skill" \
  --body "The Python snippet uses an older client-library version. Please update to v2.0." \
  --label "bug"

Replace the title, body, and label values with your specific situation. Available labels can be discovered with gh label list --repo google/skills.

Referencing Issues in Documentation

When documenting workarounds or known limitations, link directly to the relevant issue:

If you encounter this problem, please see
[#1234](https://github.com/google/skills/issues/1234)
for updates and resolution status.

Types of Issues Tracked in google/skills

Based on the project's scope, the issue tracker handles several specific categories:

Issue Type	Description	Example
Bug reports	Incorrect code examples, broken links, failing tests	Outdated BigQuery client library usage
Skill requests	Proposals for new skills covering additional Google Cloud services	Request for Cloud Run job deployment skill
SDK pattern updates	Modernization of examples to match current best practices	Migration from v1 to v2 client libraries
Security anti-patterns	Identification of potentially unsafe code examples	Hardcoded credentials in example snippets
Documentation	Clarifications, corrections, or expansion of skill explanations	Missing prerequisites for Apache Beam skill

Key Files That Define Issue Management

Two files establish the authoritative rules for how issues are managed in the Google Skills project:

README.md

Located at the repository root, this file contains the primary instruction directing users to the issue tracker. Lines 70-73 provide the canonical guidance for where and how to file issues ¹.

CONTRIBUTING.md

This file enforces the no-external-PR policy and reinforces the issue-only contribution model. Lines 17-23 explicitly redirect all potential contributors to the issue tracker rather than accepting code submissions ².

Summary

• Google Skills uses GitHub Issues exclusively at google/skills/issues for all bug reports, feature requests, and skill suggestions
• External pull requests are rejected — contributions happen only through issue filing per CONTRIBUTING.md lines 17-23
• Internal Google teams triage, label, and resolve all issues with public thread updates
• Command-line issue creation is supported via gh issue create --repo google/skills
• Two key documents — README.md and CONTRIBUTING.md — define the complete issue management policy

Frequently Asked Questions

How do I report a bug in the google/skills repository?

Open a GitHub issue at https://github.com/google/skills/issues with a clear description of the problem, steps to reproduce, and the specific skill or file affected. Use the bug label if available. Do not submit a pull request with a fix, as external PRs are not accepted.

Can I submit a pull request to fix an issue in google/skills?

No. The CONTRIBUTING.md file explicitly states that external pull requests are not accepted. All fixes must be reported as issues and will be implemented by internal Google teams. This policy applies to code changes, documentation corrections, and example updates.

How are new skill requests handled in the google/skills project?

Submit a GitHub issue describing the proposed skill, including which Google Cloud service it should cover, the use case it addresses, and any reference implementations. The internal team reviews these requests, prioritizes them against the roadmap, and implements approved skills directly.

What labels should I use when creating a google/skills issue?

Use standard GitHub labels that match your issue type: bug for problems, enhancement for feature requests, documentation for README or guide improvements, and security for vulnerability reports. If uncertain, leave labels blank — the triage team will categorize appropriately.

Footnotes

1. README.md lines 70-73 — https://github.com/google/skills/blob/main/README.md ↩ ↩²

2. CONTRIBUTING.md lines 17-23 — https://github.com/google/skills/blob/main/CONTRIBUTING.md ↩ ↩²

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}