{"owner":"deepspeedai","repo":"DeepSpeed","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["CLAUDE.md","AGENTS.md"],"files":{"CLAUDE.md":"<!-- This file is duplicated as CLAUDE.md and AGENTS.md. Keep them in sync. -->\n# AGENTS.md — Workspace-level instructions for AI coding agents\n\n## DeepSpeed Project Rules\n\n### Commit & CI requirements\n\n- All non-merge commits MUST have a `Signed-off-by` line (use `--signoff`). Get the name and email from `git config user.name` / `git config user.email`.\n- Formatting: yapf (column_limit=119, `.style.yapf`) + flake8 (`.flake8`).\n- Always verify changed files pass pre-commit checks before committing: `pre-commit run --files <changed_files>`. Only check modified files, not the entire codebase. Config: `.pre-commit-config.yaml`.\n- `check-torchdist` hook: NEVER directly import torch's distributed module. Use `import deepspeed.comm as dist` instead.\n- New files require license header:\n  ```\n  # SPDX-License-Identifier: Apache-2.0\n  # DeepSpeed Team\n  ```\n\n### Code change discipline\n\n- NEVER make cosmetic/formatting-only changes to existing code. Only add/modify lines that are functionally necessary. Minimizing diff noise is critical for code review.\n- Delete dead code decisively — if code is unused at runtime (only referenced in tests), remove it along with its tests.\n- Prefer consolidating tests over proliferating test files.\n- Blend in: when modifying code, read the surrounding context and match the style of neighboring code (naming, spacing, patterns, idioms).\n- Write beginner-friendly code: avoid deeply nested expressions or chained logic. Break complex expressions into clear, named intermediate steps.\n- Comments should explain **why**, not **what**. Describe the purpose and reasoning, not the mechanics that the code already shows.\n- New features must include corresponding tests and documentation updates.\n\n## Tool Caveats\n\n### Edit tool auto-formatter\n\nThe Edit tool has a hidden auto-formatter that silently changes quotes, whitespace, blank lines, and line wrapping. For format-sensitive modifications (e.g., when exact formatting matters for pre-commit), use `bash` with `sed`, `python`, or `cat` instead.\n","AGENTS.md":"<!-- This file is duplicated as CLAUDE.md and AGENTS.md. Keep them in sync. -->\n# AGENTS.md — Workspace-level instructions for AI coding agents\n\n## DeepSpeed Project Rules\n\n### Commit & CI requirements\n\n- All non-merge commits MUST have a `Signed-off-by` line (use `--signoff`). Get the name and email from `git config user.name` / `git config user.email`.\n- Formatting: yapf (column_limit=119, `.style.yapf`) + flake8 (`.flake8`).\n- Always verify changed files pass pre-commit checks before committing: `pre-commit run --files <changed_files>`. Only check modified files, not the entire codebase. Config: `.pre-commit-config.yaml`.\n- `check-torchdist` hook: NEVER directly import torch's distributed module. Use `import deepspeed.comm as dist` instead.\n- New files require license header:\n  ```\n  # SPDX-License-Identifier: Apache-2.0\n  # DeepSpeed Team\n  ```\n\n### Code change discipline\n\n- NEVER make cosmetic/formatting-only changes to existing code. Only add/modify lines that are functionally necessary. Minimizing diff noise is critical for code review.\n- Delete dead code decisively — if code is unused at runtime (only referenced in tests), remove it along with its tests.\n- Prefer consolidating tests over proliferating test files.\n- Blend in: when modifying code, read the surrounding context and match the style of neighboring code (naming, spacing, patterns, idioms).\n- Write beginner-friendly code: avoid deeply nested expressions or chained logic. Break complex expressions into clear, named intermediate steps.\n- Comments should explain **why**, not **what**. Describe the purpose and reasoning, not the mechanics that the code already shows.\n- New features must include corresponding tests and documentation updates.\n\n## Tool Caveats\n\n### Edit tool auto-formatter\n\nThe Edit tool has a hidden auto-formatter that silently changes quotes, whitespace, blank lines, and line wrapping. For format-sensitive modifications (e.g., when exact formatting matters for pre-commit), use `bash` with `sed`, `python`, or `cat` instead.\n"}}