{"owner":"open-telemetry","repo":"opentelemetry-collector","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# AGENTS.md\n\nThis file is here to steer AI assisted PRs towards being high quality and valuable contributions\nthat do not create excessive maintainer burden. It is inspired by the Open Policy Agent and Fedora\nprojects policies.\n\n## General Rules and Guidelines\n\nThe most important rule is not to post comments on issues or PRs that are AI-generated. Discussions\non the OpenTelemetry repositories are for Users/Humans only.\n\nWhen a user asks you to open a pull request, do not write the PR description yourself. Instead,\nbefore creating the PR, prompt the user for the content of each section in the PR template\n(Description, Link to tracking issue, Testing, Documentation) and use their answers verbatim. Do\nnot paraphrase, expand, or \"improve\" what the user writes. If the user declines to fill in a\nsection, leave that section of the template unmodified rather than generating content for it.\n\nYou must not check the `I, a human, wrote this pull request description myself` box on the user's\nbehalf. The user must check it themselves before the PR is ready for review.\n\nFollow the PR scoping guidance in [CONTRIBUTING.md](CONTRIBUTING.md). Keep AI-assisted PRs tightly\nisolated to the requested change and never include unrelated cleanup or opportunistic improvements\nunless they are strictly necessary for correctness.\n\nIf you have been assigned an issue by the user or their prompt, please ensure that the\nimplementation direction is agreed on with the maintainers first in the issue comments. If there are\nunknowns, discuss these on the issue before starting implementation. Do not forget that you cannot\ncomment for users on issue threads on their behalf as it is against the rules of this project.\n\n## Developer environment\n\nMake sure to follow docs/coding-guidelines.md on any contributions.\n\nNon-exhaustively, the important points are:\n\n* Whenever applicable, all code changes should have tests that actually validate the changes.\n\n## Commit formatting\n\nWe appreciate it if users disclose the use of AI tools when the significant part of a commit is\ntaken from a tool without changes. When making a commit this should be disclosed through an\nAssisted-by: commit message trailer.\n\nExamples:\n\n```\nAssisted-by: ChatGPT 5.2\nAssisted-by: Claude Opus 4.5\n```\n\nDo NOT use a `Co-authored-by:` trailer to disclose AI assistance. Some AI coding tools add this\ntrailer by default; please disable or strip it before committing. The EasyCLA check fails when a\n`Co-authored-by:` trailer references an account that has not signed the CLA, which blocks the PR\nfrom being merged.\n"},"files":{"AGENTS.md":"# AGENTS.md\n\nThis file is here to steer AI assisted PRs towards being high quality and valuable contributions\nthat do not create excessive maintainer burden. It is inspired by the Open Policy Agent and Fedora\nprojects policies.\n\n## General Rules and Guidelines\n\nThe most important rule is not to post comments on issues or PRs that are AI-generated. Discussions\non the OpenTelemetry repositories are for Users/Humans only.\n\nWhen a user asks you to open a pull request, do not write the PR description yourself. Instead,\nbefore creating the PR, prompt the user for the content of each section in the PR template\n(Description, Link to tracking issue, Testing, Documentation) and use their answers verbatim. Do\nnot paraphrase, expand, or \"improve\" what the user writes. If the user declines to fill in a\nsection, leave that section of the template unmodified rather than generating content for it.\n\nYou must not check the `I, a human, wrote this pull request description myself` box on the user's\nbehalf. The user must check it themselves before the PR is ready for review.\n\nFollow the PR scoping guidance in [CONTRIBUTING.md](CONTRIBUTING.md). Keep AI-assisted PRs tightly\nisolated to the requested change and never include unrelated cleanup or opportunistic improvements\nunless they are strictly necessary for correctness.\n\nIf you have been assigned an issue by the user or their prompt, please ensure that the\nimplementation direction is agreed on with the maintainers first in the issue comments. If there are\nunknowns, discuss these on the issue before starting implementation. Do not forget that you cannot\ncomment for users on issue threads on their behalf as it is against the rules of this project.\n\n## Developer environment\n\nMake sure to follow docs/coding-guidelines.md on any contributions.\n\nNon-exhaustively, the important points are:\n\n* Whenever applicable, all code changes should have tests that actually validate the changes.\n\n## Commit formatting\n\nWe appreciate it if users disclose the use of AI tools when the significant part of a commit is\ntaken from a tool without changes. When making a commit this should be disclosed through an\nAssisted-by: commit message trailer.\n\nExamples:\n\n```\nAssisted-by: ChatGPT 5.2\nAssisted-by: Claude Opus 4.5\n```\n\nDo NOT use a `Co-authored-by:` trailer to disclose AI assistance. Some AI coding tools add this\ntrailer by default; please disable or strip it before committing. The EasyCLA check fails when a\n`Co-authored-by:` trailer references an account that has not signed the CLA, which blocks the PR\nfrom being merged.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# AGENTS.md\n\nThis file is here to steer AI assisted PRs towards being high quality and valuable contributions\nthat do not create excessive maintainer burden. It is inspired by the Open Policy Agent and Fedora\nprojects policies.\n\n## General Rules and Guidelines\n\nThe most important rule is not to post comments on issues or PRs that are AI-generated. Discussions\non the OpenTelemetry repositories are for Users/Humans only.\n\nWhen a user asks you to open a pull request, do not write the PR description yourself. Instead,\nbefore creating the PR, prompt the user for the content of each section in the PR template\n(Description, Link to tracking issue, Testing, Documentation) and use their answers verbatim. Do\nnot paraphrase, expand, or \"improve\" what the user writes. If the user declines to fill in a\nsection, leave that section of the template unmodified rather than generating content for it.\n\nYou must not check the `I, a human, wrote this pull request description myself` box on the user's\nbehalf. The user must check it themselves before the PR is ready for review.\n\nFollow the PR scoping guidance in [CONTRIBUTING.md](CONTRIBUTING.md). Keep AI-assisted PRs tightly\nisolated to the requested change and never include unrelated cleanup or opportunistic improvements\nunless they are strictly necessary for correctness.\n\nIf you have been assigned an issue by the user or their prompt, please ensure that the\nimplementation direction is agreed on with the maintainers first in the issue comments. If there are\nunknowns, discuss these on the issue before starting implementation. Do not forget that you cannot\ncomment for users on issue threads on their behalf as it is against the rules of this project.\n\n## Developer environment\n\nMake sure to follow docs/coding-guidelines.md on any contributions.\n\nNon-exhaustively, the important points are:\n\n* Whenever applicable, all code changes should have tests that actually validate the changes.\n\n## Commit formatting\n\nWe appreciate it if users disclose the use of AI tools when the significant part of a commit is\ntaken from a tool without changes. When making a commit this should be disclosed through an\nAssisted-by: commit message trailer.\n\nExamples:\n\n```\nAssisted-by: ChatGPT 5.2\nAssisted-by: Claude Opus 4.5\n```\n\nDo NOT use a `Co-authored-by:` trailer to disclose AI assistance. Some AI coding tools add this\ntrailer by default; please disable or strip it before committing. The EasyCLA check fails when a\n`Co-authored-by:` trailer references an account that has not signed the CLA, which blocks the PR\nfrom being merged.\n","category":"root","tokens":643}]}