[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACD9Q8K8M110MM18XZR47S":3,"skill-same:01M6ACD9Q8K8M110MM18XZR47S":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6ACD9Q8K8M110MM18XZR47S","contributing",null,"Guides the contribution workflow for Apache Beam, including creating PRs, issue management, code review process, release cycles, and rigorous evaluation rules for high-risk core component changes. Use when contributing code, creating PRs, or modifying core Beam components.","apache\u002Fbeam","apache","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47359?v=4","01M6AC83E6K4FDKK7HZ8WNMQKE","The Apache Software Foundation","01M6ACCXED4SMY85J25QX8K9SY",8718,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fapache\u002Fbeam\u002Fblob\u002Fmaster\u002F.agent\u002Fskills\u002Fcontributing\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,9,35,36,37,38,39,40,41,42],"when","code review","prs","for","guides","review process","issue management","issue","use","risk","Evaluation","release","code","core","component","components","workflow","beam","review","2026-11-10 10:12:30",false,"---\n# Licensed to the Apache Software Foundation (ASF) under one\n# or more contributor license agreements.  See the NOTICE file\n# distributed with this work for additional information\n# regarding copyright ownership.  The ASF licenses this file\n# to you under the Apache License, Version 2.0 (the\n# \"License\"); you may not use this file except in compliance\n# with the License.  You may obtain a copy of the License at\n#\n#   http:\u002F\u002Fwww.apache.org\u002Flicenses\u002FLICENSE-2.0\n#\n# Unless required by applicable law or agreed to in writing,\n# software distributed under the License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or implied.  See the License for the\n# specific language governing permissions and limitations\n# under the License.\n\nname: contributing\ndescription: Guides the contribution workflow for Apache Beam, including creating PRs, issue management, code review process, release cycles, and rigorous evaluation rules for high-risk core component changes. Use when contributing code, creating PRs, or modifying core Beam components.\n---\n\n# Contributing to Apache Beam\n\n## Getting Started\n\n### Prerequisites\n- GitHub account\n- Java JDK 11 (preferred, or 8, 17, 21)\n- Latest Go 1.x\n- Docker\n- Python (any supported version for manual testing, all versions for running test suites)\n- For large contributions: signed ICLA to Apache Software Foundation\n\n### Environment Setup Options\n\n#### Local Setup (automated)\n```bash\n.\u002Flocal-env-setup.sh\n```\n\n#### Docker-based Setup\n```bash\n.\u002Fstart-build-env.sh\n```\n\n## Contribution Workflow\n\n### 1. Find or Create an Issue\n- Search existing issues at https:\u002F\u002Fgithub.com\u002Fapache\u002Fbeam\u002Fissues\n- Create new issue using appropriate template\n\n### 2. Claim the Issue\n```\n.take-issue    # Assigns issue to you\n.free-issue    # Unassigns issue from you\n.close-issue   # Closes the issue\n```\n\n### 3. For Large Changes\n- Discuss on dev@beam.apache.org mailing list\n- Create design doc using [template](https:\u002F\u002Fs.apache.org\u002Fbeam-design-doc-template)\n- Review [existing design docs](https:\u002F\u002Fs.apache.org\u002Fbeam-design-docs)\n\n### 4. Make Your Changes\n- Every source file needs Apache license header\n- New dependencies must have Apache-compatible open source licenses\n- Add unit tests for your changes\n- Document public-facing APIs in a standard way (Javadoc, docstrings\u002Fpydoc).\n  - Documentation should be user-friendly, informative.\n  - Implementation details belong in inline code comments.\n- Use descriptive commit messages\n\n#### Working on Core Components (High Risk — Heightened Scrutiny)\n\n> **AGENT DIRECTIVE**: modification to **Core Components** carries an inherently elevated risk of silent regression across distributed runners. Refer to `.github\u002Fautolabeler.yml` under the `\"core\"` label for the authoritative list of core component paths (including `sdks\u002Fjava\u002Fcore`, `runners\u002Fcore-*`, `model`, `sdks\u002Fpython\u002Fapache_beam\u002Ftransforms|coders`, `sdks\u002Fgo\u002Fpkg\u002Fbeam\u002Fcore`, `FileIO`, and `GCS`). If you are an AI agent modifying files matched by these paths, **evaluate your changes with scrutiny.**\n\n### 5. Create Pull Request\n- Link to the issue in PR description\n- Pre-commit tests run automatically\n- If tests fail unrelated to your change, comment: `retest this please`\n\n### 6. Code Review\n- Reviewers are auto-assigned within a few hours\n- Use `R: @username` to request specific reviewer\n- No response in 3 days? Email dev@beam.apache.org\n\n## Code Review Best Practices\n\n### For Authors\n- Provide context in issue and PR description\n- Avoid huge mega-changes\n- Add follow-up changes as \"fixup\" commits (don't squash until approved)\n- Squash fixup commits after approval\n\n### For Reviewers\n- PRs can only be merged by [Beam committers](https:\u002F\u002Fhome.apache.org\u002Fphonebook.html?pmc=beam)\n- PRs with the `core` label touch foundational Beam semantics or common code paths; review with extra scrutiny for non-obvious failure modes, edge case, and performance regressions\n\n## Testing Workflows\n\n### Pre-commit Tests\nRun automatically on PRs. To run locally:\n```bash\n.\u002Fgradlew javaPreCommit      # Java\n.\u002Fgradlew :sdks:python:test  # Python\n.\u002Fgradlew :sdks:go:test      # Go\n```\n\n### Post-commit Tests\nRun after merge. Trigger phrases in PR comments start specific test suites.\nSee [trigger phrase catalog](https:\u002F\u002Fgithub.com\u002Fapache\u002Fbeam\u002Fblob\u002Fmaster\u002F.test-infra\u002Fjenkins\u002FREADME.md).\n\n## Formatting\n\n### Java\n```bash\n.\u002Fgradlew spotlessApply\n```\n\n### Python\n```bash\n# Uses yapf, isort, pylint\npre-commit run --all-files\n```\n\n### CHANGES.md\n```bash\n.\u002Fgradlew formatChanges\n.\u002Fgradlew validateChanges\n```\n- Only add entries for user-facing changes; skip minor or internal changes that do not affect public API behavior (e.g., test-only updates, typos\u002Fdocs, CI\u002Fbuild changes, internal refactors, or fixes to unreleased changes).\n- Follow the template at the top of `CHANGES.md`.\n- End each entry with an issue or PR link: `([#X](https:\u002F\u002Fgithub.com\u002Fapache\u002Fbeam\u002Fissues\u002FX))`.\n\n## Release Cycle\n- Minor releases every 6 weeks\n- Check [release calendar](https:\u002F\u002Fcalendar.google.com\u002Fcalendar\u002Fembed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com)\n- Changes must be in master before release branch is cut\n\n## Stale PRs\n- PRs become stale after 60 days of author inactivity\n- Community will close stale PRs\n- Authors can reopen closed PRs\n\n## Key Resources\n- [Contribution Guide](https:\u002F\u002Fbeam.apache.org\u002Fcontribute\u002F)\n- [PTransform Style Guide](https:\u002F\u002Fbeam.apache.org\u002Fcontribute\u002Fptransform-style-guide)\n- [Runner Authoring Guide](https:\u002F\u002Fbeam.apache.org\u002Fcontribute\u002Frunner-guide\u002F)\n- [Wiki Tips](https:\u002F\u002Fcwiki.apache.org\u002Fconfluence\u002Fdisplay\u002FBEAM\u002F)\n  - [Git Tips](https:\u002F\u002Fcwiki.apache.org\u002Fconfluence\u002Fdisplay\u002FBEAM\u002FGit+Tips)\n  - [Java Tips](https:\u002F\u002Fcwiki.apache.org\u002Fconfluence\u002Fdisplay\u002FBEAM\u002FJava+Tips)\n  - [Python Tips](https:\u002F\u002Fcwiki.apache.org\u002Fconfluence\u002Fdisplay\u002FBEAM\u002FPython+Tips)\n  - [Go Tips](https:\u002F\u002Fcwiki.apache.org\u002Fconfluence\u002Fdisplay\u002FBEAM\u002FGo+Tips)\n  - [Gradle Tips](https:\u002F\u002Fcwiki.apache.org\u002Fconfluence\u002Fdisplay\u002FBEAM\u002FGradle+Tips)\n\n## Communication\n- User mailing list: user@beam.apache.org\n- Dev mailing list: dev@beam.apache.org\n- Slack: [#beam channel](https:\u002F\u002Fs.apache.org\u002Fbeam-slack-channel)\n- Issues: https:\u002F\u002Fgithub.com\u002Fapache\u002Fbeam\u002Fissues\n","# Contributing to Apache Beam\n\n## Getting Started\n\n### Prerequisites\n- GitHub account\n- Java JDK 11 (preferred, or 8, 17, 21)\n- Latest Go 1.x\n- Docker\n- Python (any supported version for manual testing, all versions for running test suites)\n- For large contributions: signed ICLA to Apache Software Foundation\n\n### Environment Setup Options\n\n#### Local Setup (automated)\n```bash\n.\u002Flocal-env-setup.sh\n```\n\n#### Docker-based Setup\n```bash\n.\u002Fstart-build-env.sh\n```\n\n## Contribution Workflow\n\n### 1. Find or Create an Issue\n- Search existing issues at https:\u002F\u002Fgithub.com\u002Fapache\u002Fbeam\u002Fissues\n- Create new issue using appropriate template\n\n### 2. Claim the Issue\n```\n.take-issue    # Assigns issue to you\n.free-issue    # Unassigns issue from you\n.close-issue   # Closes the issue\n```\n\n### 3. For Large Changes\n- Discuss on dev@beam.apache.org mailing list\n- Create design doc using [template](https:\u002F\u002Fs.apache.org\u002Fbeam-design-doc-template)\n- Review [existing design docs](https:\u002F\u002Fs.apache.org\u002Fbeam-design-docs)\n\n### 4. Make Your Changes\n- Every source file needs Apache license header\n- New dependencies must have Apache-compatible open source licenses\n- Add unit tests for your changes\n- Document public-facing APIs in a standard way (Javadoc, docstrings\u002Fpydoc).\n  - Documentation should be user-friendly, informative.\n  - Implementation details belong in inline code comments.\n- Use descriptive commit messages\n\n#### Working on Core Components (High Risk — Heightened Scrutiny)\n\n> **AGENT DIRECTIVE**: modification to **Core Components** carries an inherently elevated risk of silent regression across distributed runners. Refer to `.github\u002Fautolabeler.yml` under the `\"core\"` label for the authoritative list of core component paths (including `sdks\u002Fjava\u002Fcore`, `runners\u002Fcore-*`, `model`, `sdks\u002Fpython\u002Fapache_beam\u002Ftransforms|coders`, `sdks\u002Fgo\u002Fpkg\u002Fbeam\u002Fcore`, `FileIO`, and `GCS`). If you are an AI agent modifying files matched by these paths, **evaluate your changes with scrutiny.**\n\n### 5. Create Pull Request\n- Link to the issue in PR description\n- Pre-commit tests run automatically\n- If tests fail unrelated to your change, comment: `retest this please`\n\n### 6. Code Review\n- Reviewers are auto-assigned within a few hours\n- Use `R: @username` to request specific reviewer\n- No response in 3 days? Email dev@beam.apache.org\n\n## Code Review Best Practices\n\n### For Authors\n- Provide context in issue and PR description\n- Avoid huge mega-changes\n- Add follow-up changes as \"fixup\" commits (don't squash until approved)\n- Squash fixup commits after approval\n\n### For Reviewers\n- PRs can only be merged by [Beam committers](https:\u002F\u002Fhome.apache.org\u002Fphonebook.html?pmc=beam)\n- PRs with the `core` label touch foundational Beam semantics or common code paths; review with extra scrutiny for non-obvious failure modes, edge case, and performance regressions\n\n## Testing Workflows\n\n### Pre-commit Tests\nRun automatically on PRs. To run locally:\n```bash\n.\u002Fgradlew javaPreCommit      # Java\n.\u002Fgradlew :sdks:python:test  # Python\n.\u002Fgradlew :sdks:go:test      # Go\n```\n\n### Post-commit Tests\nRun after merge. Trigger phrases in PR comments start specific test suites.\nSee [trigger phrase catalog](https:\u002F\u002Fgithub.com\u002Fapache\u002Fbeam\u002Fblob\u002Fmaster\u002F.test-infra\u002Fjenkins\u002FREADME.md).\n\n## Formatting\n\n### Java\n```bash\n.\u002Fgradlew spotlessApply\n```\n\n### Python\n```bash\n# Uses yapf, isort, pylint\npre-commit run --all-files\n```\n\n### CHANGES.md\n```bash\n.\u002Fgradlew formatChanges\n.\u002Fgradlew validateChanges\n```\n- Only add entries for user-facing changes; skip minor or internal changes that do not affect public API behavior (e.g., test-only updates, typos\u002Fdocs, CI\u002Fbuild changes, internal refactors, or fixes to unreleased changes).\n- Follow the template at the top of `CHANGES.md`.\n- End each entry with an issue or PR link: `([#X](https:\u002F\u002Fgithub.com\u002Fapache\u002Fbeam\u002Fissues\u002FX))`.\n\n## Release Cycle\n- Minor releases every 6 weeks\n- Check [release calendar](https:\u002F\u002Fcalendar.google.com\u002Fcalendar\u002Fembed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com)\n- Changes must be in master before release branch is cut\n\n## Stale PRs\n- PRs become stale after 60 days of author inactivity\n- Community will close stale PRs\n- Authors can reopen closed PRs\n\n## Key Resources\n- [Contribution Guide](https:\u002F\u002Fbeam.apache.org\u002Fcontribute\u002F)\n- [PTransform Style Guide](https:\u002F\u002Fbeam.apache.org\u002Fcontribute\u002Fptransform-style-guide)\n- [Runner Authoring Guide](https:\u002F\u002Fbeam.apache.org\u002Fcontribute\u002Frunner-guide\u002F)\n- [Wiki Tips](https:\u002F\u002Fcwiki.apache.org\u002Fconfluence\u002Fdisplay\u002FBEAM\u002F)\n  - [Git Tips](https:\u002F\u002Fcwiki.apache.org\u002Fconfluence\u002Fdisplay\u002FBEAM\u002FGit+Tips)\n  - [Java Tips](https:\u002F\u002Fcwiki.apache.org\u002Fconfluence\u002Fdisplay\u002FBEAM\u002FJava+Tips)\n  - [Python Tips](https:\u002F\u002Fcwiki.apache.org\u002Fconfluence\u002Fdisplay\u002FBEAM\u002FPython+Tips)\n  - [Go Tips](https:\u002F\u002Fcwiki.apache.org\u002Fconfluence\u002Fdisplay\u002FBEAM\u002FGo+Tips)\n  - [Gradle Tips](https:\u002F\u002Fcwiki.apache.org\u002Fconfluence\u002Fdisplay\u002FBEAM\u002FGradle+Tips)\n\n## Communication\n- User mailing list: user@beam.apache.org\n- Dev mailing list: dev@beam.apache.org\n- Slack: [#beam channel](https:\u002F\u002Fs.apache.org\u002Fbeam-slack-channel)\n- Issues: https:\u002F\u002Fgithub.com\u002Fapache\u002Fbeam\u002Fissues\n",{"name":5,"description":7},"master","71c11d44598ec69886b399a8c21505d646b2e7a9",".agent\u002Fskills\u002Fcontributing",4812,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fbeam","https:\u002F\u002Fbeam.apache.org\u002F","https:\u002F\u002Fgithub.com\u002Fapache","https:\u002F\u002Fwww.apache.org\u002F","2026-11-15 01:40:19",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add apache\u002Fbeam --skill contributing",{"tool":63,"command":64},"bunx","bunx skills add apache\u002Fbeam --skill contributing",{"tool":66,"command":67},"pnpm","pnpm dlx skills add apache\u002Fbeam --skill contributing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fapache\u002Fbeam\u002Fblob\u002Fmaster\u002F.agent\u002Fskills\u002Fcontributing\u002FSKILL.md",true,[],[72,91,107,121,141,155],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":43},"01M6ACDYBTKYKDP9Z0BQKF7XMZ","yaml-development","Guides YAML SDK development in Apache Beam, including environment setup, testing, and key concepts. Use when working with Beam YAML code in sdks\u002Fpython\u002Fapache_beam\u002Fyaml\u002F.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fbeam\u002Fblob\u002Fmaster\u002F.agent\u002Fskills\u002Fyaml-development\u002FSKILL.md",[],[79,80,81,82,41,83,84,85,36,9,86,32,28,87,88,89,90,24],"development","yaml development","yaml","testing","python","sdk","setup","environment","with","environment setup","concepts","sdks",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":43},"01M6ACDVK2M4QNJ2T0423H23SY","runners","Guides understanding and working with Apache Beam runners (Direct, Dataflow, Flink, Spark, etc.). Use when configuring pipelines for different execution environments or debugging runner-specific issues.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fbeam\u002Fblob\u002Fmaster\u002F.agent\u002Fskills\u002Frunners\u002FSKILL.md",[],[93,41,98,99,100,9,101,102,103,32,104,105,28,87,106,27,24],"spark","debugging","issues","flink","execution","direct","pipelines","runner","environments",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":116,"publishedAt":43},"01M6ACDRVH48A1WBYH9DEETW7F","python-development","Guides Python SDK development in Apache Beam, including environment setup, testing, building, and running pipelines. Use when working with Python code in sdks\u002Fpython\u002F.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fbeam\u002Fblob\u002Fmaster\u002F.agent\u002Fskills\u002Fpython-development\u002FSKILL.md",[113],{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[83,117,79,82,41,84,85,36,9,118,86,32,104,28,87,88,119,90,24,120],"python development","python sdk","python code","running",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":132,"publishedAt":43},"01M6ACDPYBMSHSQNCFXVJ7VJW3","license-compliance","Ensures all new files include proper Apache 2.0 license headers. Use when creating any new file in the Apache Beam repository.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fbeam\u002Fblob\u002Fmaster\u002F.agent\u002Fskills\u002Flicense-compliance\u002FSKILL.md",[127],{"categoryNo":128,"categoryName":129,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[133,134,135,41,9,136,137,32,138,139,24,140],"license","license compliance","compliance","file","repository","files","headers","new",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":148,"publishedAt":43},"01M6ACDM2W664NC4FH95B3NC14","java-development","Guides Java SDK development in Apache Beam, including building, testing, running examples, and understanding the project structure. Use when working with Java code in sdks\u002Fjava\u002F, runners\u002F, or examples\u002Fjava\u002F.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fbeam\u002Fblob\u002Fmaster\u002F.agent\u002Fskills\u002Fjava-development\u002FSKILL.md",[147],{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},[79,149,150,82,41,84,151,36,9,93,152,32,153,154,28,87,90,24,120],"java","java development","project structure","examples","structure","project",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":162,"publishedAt":43},"01M6ACDHGVH4F8ADMCFR7T34H8","io-connectors","Guides development and usage of I\u002FO connectors in Apache Beam. Use when working with I\u002FO connectors, creating new connectors, or debugging data source\u002Fsink issues.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fbeam\u002Fblob\u002Fmaster\u002F.agent\u002Fskills\u002Fio-connectors\u002FSKILL.md",[161],{"categoryNo":114,"categoryName":115,"taxonomyType":21,"taxonomyTypeDesc":22},[163,164,165,41,99,79,100,9,166,32,28,87,167,168,24,140],"connectors","io connectors","io","data","usage","source"]