{"owner":"kvcache-ai","repo":"Mooncake","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# AGENTS.md\n\n## `docs/` Directory Changes\n\n- Before modifying files under `docs/`, read `docs/AGENTS.md`.\n\n## Pull Request Guidelines\n\n- Follow `CONTRIBUTING.md` for PR title prefixes, RFC expectations, and\n  contribution workflow.\n- Before opening a PR for nontrivial work, check whether an existing issue or\n  open PR already covers the same change. If the work overlaps, explain the\n  difference instead of duplicating it.\n- Do not open low-value busywork PRs for isolated typo, style, or mechanical\n  changes unless they are part of a substantive requested change.\n- Use `.github/pull_request_template.md` when preparing a PR, and fill in the\n  relevant sections for description, module, type of change, testing,\n  checklist, and AI assistance disclosure.\n- For AI-assisted changes, make sure the human submitter has reviewed every\n  changed line and can defend the change end-to-end.\n- Before handoff, run pre-commit on the files touched by the change when the\n  toolchain is available (see `CONTRIBUTING.md` for the PR-scoped\n  `pre-commit run --files ...` command). Do not use\n  `pre-commit run --all-files` for routine PRs; if it rewrites unrelated\n  files, leave those edits out of the PR.\n- Keep PRs lean: review `git diff` before staging, and include only changes\n  required for the requested task.\n"},"files":{"AGENTS.md":"# AGENTS.md\n\n## `docs/` Directory Changes\n\n- Before modifying files under `docs/`, read `docs/AGENTS.md`.\n\n## Pull Request Guidelines\n\n- Follow `CONTRIBUTING.md` for PR title prefixes, RFC expectations, and\n  contribution workflow.\n- Before opening a PR for nontrivial work, check whether an existing issue or\n  open PR already covers the same change. If the work overlaps, explain the\n  difference instead of duplicating it.\n- Do not open low-value busywork PRs for isolated typo, style, or mechanical\n  changes unless they are part of a substantive requested change.\n- Use `.github/pull_request_template.md` when preparing a PR, and fill in the\n  relevant sections for description, module, type of change, testing,\n  checklist, and AI assistance disclosure.\n- For AI-assisted changes, make sure the human submitter has reviewed every\n  changed line and can defend the change end-to-end.\n- Before handoff, run pre-commit on the files touched by the change when the\n  toolchain is available (see `CONTRIBUTING.md` for the PR-scoped\n  `pre-commit run --files ...` command). Do not use\n  `pre-commit run --all-files` for routine PRs; if it rewrites unrelated\n  files, leave those edits out of the PR.\n- Keep PRs lean: review `git diff` before staging, and include only changes\n  required for the requested task.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# AGENTS.md\n\n## `docs/` Directory Changes\n\n- Before modifying files under `docs/`, read `docs/AGENTS.md`.\n\n## Pull Request Guidelines\n\n- Follow `CONTRIBUTING.md` for PR title prefixes, RFC expectations, and\n  contribution workflow.\n- Before opening a PR for nontrivial work, check whether an existing issue or\n  open PR already covers the same change. If the work overlaps, explain the\n  difference instead of duplicating it.\n- Do not open low-value busywork PRs for isolated typo, style, or mechanical\n  changes unless they are part of a substantive requested change.\n- Use `.github/pull_request_template.md` when preparing a PR, and fill in the\n  relevant sections for description, module, type of change, testing,\n  checklist, and AI assistance disclosure.\n- For AI-assisted changes, make sure the human submitter has reviewed every\n  changed line and can defend the change end-to-end.\n- Before handoff, run pre-commit on the files touched by the change when the\n  toolchain is available (see `CONTRIBUTING.md` for the PR-scoped\n  `pre-commit run --files ...` command). Do not use\n  `pre-commit run --all-files` for routine PRs; if it rewrites unrelated\n  files, leave those edits out of the PR.\n- Keep PRs lean: review `git diff` before staging, and include only changes\n  required for the requested task.\n","category":"root","tokens":328}]}