This file is for coding agents working in this repository. It summarizes the project shape and points to the source-of-truth docs that should be followed when changing code.
- Keep this root
AGENTS.mdunder about 120 lines. - Keep subtree
AGENTS.mdfiles under about 100 lines and focused on local ownership, commands, and pitfalls. - Put repeatable workflows, review procedures, and extended examples in agent skills or regular docs, then link to them from the relevant guide.
Repository skills live under .agents/skills/<skill-name>/SKILL.md. Use each
skill's frontmatter description to decide when it applies. Keep .agents as
the canonical location and add tool-specific adapters only when a tool requires
them.
- For any file you touch, read the nearest
AGENTS.mdand each parent guide up to this root guide before editing. - Keep changes scoped to the requested behavior; use
REVIEW.mdfor PR split expectations. - Prefer existing local patterns before adding new abstractions.
- Do not duplicate rules across
AGENTS.mdfiles, skills, andREVIEW.md; link to the source of truth instead. - Do not duplicate code or similar implementation patterns; use helper functions or shared utilities when appropriate.
- Do not commit generated build output, generated docs, local install directories, or editor/tool scratch files.
- Commit messages usually follow
COMPONENT/SUBCOMPONENT: Imperative message, for exampleUCP/CORE: Fix endpoint flush completion.
UCX is a C communication framework with C++ unit tests. Use the nearest subtree guide when one exists for local ownership, commands, and pitfalls:
src/AGENTS.mdfor runtime source code.test/AGENTS.mdfor test code.
Other top-level areas:
bindings: Go and Java bindings over UCX APIs.buildlib: build, packaging, and CI helper scripts.config: autotools helpers and m4 feature checks.debian: Debian packaging metadata and scripts.docs: Sphinx, Doxygen, style, and user documentation.examples: small programs that demonstrate public APIs.
Follow these project docs instead of duplicating their contents:
docs/CodeStyle.mdfor C/C++ formatting and naming.docs/LoggingStyle.mdfor log levels and message style.docs/OptimizationStyle.mdfor performance-sensitive changes.REVIEW.mdfor UCX pull-request review checks and comment style.