{"owner":"uutils","repo":"coreutils","hasSkills":true,"totalSkillsCount":1,"totalTokensCount":550,"categories":["root-instruction"],"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# AGENTS.md\n\nWriting this file is not a statement for or against using AI coding agents.\nPeople are using them in this repository either way, so this file exists to make\nsure that when they do, the project's rules are actually followed.\n\nIf you are driving an agent here, you are responsible for its output. Read the\ndiff before you send it.\n\nResponses to reviewers should be written by a human, not an agent.\n\n## Start with an issue\n\nBefore opening a PR, search for an existing issue describing the problem being\naddressed. Search both open and closed issues where relevant.\n\nWhen an existing issue covers the work, reference it in the PR.\n\nIf you have already opened a PR for the work, continue working on that PR\nrather than opening a new one to replace it. Rebase or otherwise update the\nexisting PR's branch as needed.\n\nIf the PR fully resolves an issue, include `Closes #XXXXX` in the PR\ndescription so that the issue is automatically closed when the PR is merged.\n\n## Never read or copy GNU code\n\nGNU coreutils is GPLv3; this project is MIT. Any code derived from it - even a\nfew lines, a helper structure, a test fixture or a comment - cannot be accepted.\n\n## A PR needs tests\n\nNew behavior or a bug fix comes with a test, in `tests/by-util/test_.rs`\nor as a unit test next to the code. If a GNU test used to fail and now passes,\nadd a Rust test so it cannot silently regress.\n\nNo tests, no merge.\n\n## Keep the PR description short\n\nDescribe the problem being solved and what changed. That is all.\n\n- No generated walls of text, no bullet-point summaries of every hunk, no\n emoji-headed sections.\n- Title: `: `, e.g. `ls: fix version sort order`.\n- Write issue reports, PR descriptions and replies to reviewers in your own\n words. The point of review is to check that a human understands the change.\n\n## Read the docs already in this repo\n\nBefore changing anything, look at the Markdown files here - they are the actual\nrules, this file is only a pointer:\n\n- `CONTRIBUTING.md` - licensing, commit hygiene, what a PR must contain\n- `DEVELOPMENT.md` - build, test and environment setup\n- `README.md`, `SECURITY.md`, `CODE_OF_CONDUCT.md`\n- `docs/src/*.md` - platforms, performance, l10n, multicall, test coverage\n- the per-utility `README.md` / `locales/*.ftl` files when touching a utility\n"},"files":{"AGENTS.md":"# AGENTS.md\n\nWriting this file is not a statement for or against using AI coding agents.\nPeople are using them in this repository either way, so this file exists to make\nsure that when they do, the project's rules are actually followed.\n\nIf you are driving an agent here, you are responsible for its output. Read the\ndiff before you send it.\n\nResponses to reviewers should be written by a human, not an agent.\n\n## Start with an issue\n\nBefore opening a PR, search for an existing issue describing the problem being\naddressed. Search both open and closed issues where relevant.\n\nWhen an existing issue covers the work, reference it in the PR.\n\nIf you have already opened a PR for the work, continue working on that PR\nrather than opening a new one to replace it. Rebase or otherwise update the\nexisting PR's branch as needed.\n\nIf the PR fully resolves an issue, include `Closes #XXXXX` in the PR\ndescription so that the issue is automatically closed when the PR is merged.\n\n## Never read or copy GNU code\n\nGNU coreutils is GPLv3; this project is MIT. Any code derived from it - even a\nfew lines, a helper structure, a test fixture or a comment - cannot be accepted.\n\n## A PR needs tests\n\nNew behavior or a bug fix comes with a test, in `tests/by-util/test_.rs`\nor as a unit test next to the code. If a GNU test used to fail and now passes,\nadd a Rust test so it cannot silently regress.\n\nNo tests, no merge.\n\n## Keep the PR description short\n\nDescribe the problem being solved and what changed. That is all.\n\n- No generated walls of text, no bullet-point summaries of every hunk, no\n emoji-headed sections.\n- Title: `: `, e.g. `ls: fix version sort order`.\n- Write issue reports, PR descriptions and replies to reviewers in your own\n words. The point of review is to check that a human understands the change.\n\n## Read the docs already in this repo\n\nBefore changing anything, look at the Markdown files here - they are the actual\nrules, this file is only a pointer:\n\n- `CONTRIBUTING.md` - licensing, commit hygiene, what a PR must contain\n- `DEVELOPMENT.md` - build, test and environment setup\n- `README.md`, `SECURITY.md`, `CODE_OF_CONDUCT.md`\n- `docs/src/*.md` - platforms, performance, l10n, multicall, test coverage\n- the per-utility `README.md` / `locales/*.ftl` files when touching a utility\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","rawUrl":"https://raw.githubusercontent.com/uutils/coreutils/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","content":"# AGENTS.md\n\nWriting this file is not a statement for or against using AI coding agents.\nPeople are using them in this repository either way, so this file exists to make\nsure that when they do, the project's rules are actually followed.\n\nIf you are driving an agent here, you are responsible for its output. Read the\ndiff before you send it.\n\nResponses to reviewers should be written by a human, not an agent.\n\n## Start with an issue\n\nBefore opening a PR, search for an existing issue describing the problem being\naddressed. Search both open and closed issues where relevant.\n\nWhen an existing issue covers the work, reference it in the PR.\n\nIf you have already opened a PR for the work, continue working on that PR\nrather than opening a new one to replace it. Rebase or otherwise update the\nexisting PR's branch as needed.\n\nIf the PR fully resolves an issue, include `Closes #XXXXX` in the PR\ndescription so that the issue is automatically closed when the PR is merged.\n\n## Never read or copy GNU code\n\nGNU coreutils is GPLv3; this project is MIT. Any code derived from it - even a\nfew lines, a helper structure, a test fixture or a comment - cannot be accepted.\n\n## A PR needs tests\n\nNew behavior or a bug fix comes with a test, in `tests/by-util/test_.rs`\nor as a unit test next to the code. If a GNU test used to fail and now passes,\nadd a Rust test so it cannot silently regress.\n\nNo tests, no merge.\n\n## Keep the PR description short\n\nDescribe the problem being solved and what changed. That is all.\n\n- No generated walls of text, no bullet-point summaries of every hunk, no\n emoji-headed sections.\n- Title: `: `, e.g. `ls: fix version sort order`.\n- Write issue reports, PR descriptions and replies to reviewers in your own\n words. The point of review is to check that a human understands the change.\n\n## Read the docs already in this repo\n\nBefore changing anything, look at the Markdown files here - they are the actual\nrules, this file is only a pointer:\n\n- `CONTRIBUTING.md` - licensing, commit hygiene, what a PR must contain\n- `DEVELOPMENT.md` - build, test and environment setup\n- `README.md`, `SECURITY.md`, `CODE_OF_CONDUCT.md`\n- `docs/src/*.md` - platforms, performance, l10n, multicall, test coverage\n- the per-utility `README.md` / `locales/*.ftl` files when touching a utility\n","isInternal":false,"tokens":550,"sizeBytes":2324}],"systemPromptSnippet":"\n\n# AGENTS.md\n\nWriting this file is not a statement for or against using AI coding agents.\nPeople are using them in this repository either way, so this file exists to make\nsure that when they do, the project's rules are actually followed.\n\nIf you are driving an agent here, you are responsible for its output. Read the\ndiff before you send it.\n\nResponses to reviewers should be written by a human, not an agent.\n\n## Start with an issue\n\nBefore opening a PR, search for an existing issue describing the problem being\naddressed. Search both open and closed issues where relevant.\n\nWhen an existing issue covers the work, reference it in the PR.\n\nIf you have already opened a PR for the work, continue working on that PR\nrather than opening a new one to replace it. Rebase or otherwise update the\nexisting PR's branch as needed.\n\nIf the PR fully resolves an issue, include `Closes #XXXXX` in the PR\ndescription so that the issue is automatically closed when the PR is merged.\n\n## Never read or copy GNU code\n\nGNU coreutils is GPLv3; this project is MIT. Any code derived from it - even a\nfew lines, a helper structure, a test fixture or a comment - cannot be accepted.\n\n## A PR needs tests\n\nNew behavior or a bug fix comes with a test, in `tests/by-util/test_.rs`\nor as a unit test next to the code. If a GNU test used to fail and now passes,\nadd a Rust test so it cannot silently regress.\n\nNo tests, no merge.\n\n## Keep the PR description short\n\nDescribe the problem being solved and what changed. That is all.\n\n- No generated walls of text, no bullet-point summaries of every hunk, no\n emoji-headed sections.\n- Title: `: `, e.g. `ls: fix version sort order`.\n- Write issue reports, PR descriptions and replies to reviewers in your own\n words. The point of review is to check that a human understands the change.\n\n## Read the docs already in this repo\n\nBefore changing anything, look at the Markdown files here - they are the actual\nrules, this file is only a pointer:\n\n- `CONTRIBUTING.md` - licensing, commit hygiene, what a PR must contain\n- `DEVELOPMENT.md` - build, test and environment setup\n- `README.md`, `SECURITY.md`, `CODE_OF_CONDUCT.md`\n- `docs/src/*.md` - platforms, performance, l10n, multicall, test coverage\n- the per-utility `README.md` / `locales/*.ftl` files when touching a utility\n"}