{"owner":"uutils","repo":"coreutils","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"files":{"AGENTS.md":"# AGENTS.md\n\nWriting this file is not a statement for or against using AI coding agents.\nPeople are using them on this repository either way, so this file exists to make\nsure that when they do, the rules of the project 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\nAnswers to the reviewers should be done by a human, not a agent.\n\n## 1. 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## 2. A PR needs tests\n\nNew behavior or a bug fix comes with a test, in `tests/by-util/test_<util>.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## 3. 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: `<util>: <what changed>`, 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## 4. 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"}}