↓ メインコンテンツへスキップ

google-oss

Google オープンソースリポジトリおよび Googler の個人 OSS プロジェクト向けライセンス・コンプライアンスガイド。addlicense による Apache-2.0 ヘッダー付与、LICENSE ファイル検証、必須免責事項の挿入と公開前監査を行います。

注記:以下の SKILL.md プロンプト本文は、LLM の実行精度を最大化するため英語で管理されています。

Google Open Source Compliance & License Attributions #

Audit, apply, and verify Google Open Source policy requirements, source code license headers (addlicense), and mandatory repository disclaimers.


⚡ Quick Reference: Actions & Commands #

1. Apply License Headers via addlicense #

Install the official Google addlicense tool if not already present:

bash
go install github.com/google/addlicense@latest

Apply Apache-2.0 copyright headers across all source files:

bash
$(go env GOPATH)/bin/addlicense -c "Google LLC" -l apache .

Verify/Check without modifying (CI gate):

bash
$(go env GOPATH)/bin/addlicense -check -c "Google LLC" -l apache .

Common license flag options:

  • -l apache: Apache License 2.0 (standard default for Google OSS)
  • -l mit: MIT License
  • -l bsd: BSD 3-Clause License
  • -s=only: Force SPDX short identifier style (// SPDX-License-Identifier: Apache-2.0)
  • -ignore "vendor/**": Ignore specific directory globs

2. Mandatory README Disclaimers #

Every repository published by Googlers or under Google open source that is not an official Google product MUST include the appropriate disclaimer in the root README.md.

Standard Non-Official Product Disclaimer: #

markdown
---

## Disclaimer

This is not an officially supported Google product.

Experimental / Educational Project Disclaimer: #

markdown
---

## Disclaimer

This is not an officially supported Google product. It is an experimental project created for educational and development purposes.

📋 Pre-Release Compliance Checklist #

Before publishing or tagging any public open-source repository, verify:

  1. License Header Coverage:
    • Run addlicense -check across all code files (.go, .py, .ts, .js, .rs, .c, .cpp, .sh, .proto).
    • Ensure generated files (e.g. *.pb.go) or third-party code in vendor/ or third_party/ are properly ignored or attributed.
  2. Root LICENSE File:
    • Ensure an unmodified copy of the chosen license (e.g. Apache 2.0) exists at the repository root.
  3. Non-Official Product Disclaimer:
    • Present at the bottom of root README.md.
  4. Zero Internal Contamination:
    • No internal links, internal issue trackers, intranet shortcuts, corporate credentials, or non-public project codenames.

📚 References & Scripts #