{"owner":"dbt-labs","repo":"dbt-core","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# Project Instructions (AI Agents)\n\nThese instructions are for coding agents (Codex CLI, Claude Code, etc).\n\nPaths in this file and in `.agents/` are relative to the directory containing this file.\n\n## Hard Rules\n\n### Code Style\n\n- Follow existing code style and patterns in the given crate/module.\n- Keep changes minimal and focused to the task at hand.\n- Prefer simple, readable code over clever or complex solutions.\n\n### Changelog\n\n- Never manually create or write changelog YAML files. Always use `changie new` to generate entries.\n- Run `changie new` from the repository root with flags: `changie new --kind \"<kind>\" --body \"<description>\" --custom \"project=<project>\" --custom \"issue=<number>\" --custom \"author=<handle>\" --interactive=false`\n- For optional empty fields (`issue`, `author`), prompt the user if running locally or pass a space (e.g., `--custom \"issue= \"`) then edit the generated file to replace `' '` with `\"\"`.\n\n### Running dev commands\n\n- Never run blanket `cargo` commands without `-p <crate>` unless explicitly asked.\n- Avoid context pollution: don’t paste long logs; prefer LLM-friendly JSONL output and short excerpts.\n- Avoid full builds and full test runs during iteration; keep commands scoped and fast.\n\n## Where To Look Next (Task-Specific)\n\n- Respect author preferences (optional/local): `AGENTS.local.md`\n- When working on Adapters: `.agents/adapters.md`. Adapters consist of the following crates:\n  - `dbt-adapter`\n  - `dbt-adapter-core`\n  - `dbt-adapter-sql`\n  - `dbt-auth`\n  - `dbt-sql-keywords`\n  - `dbt-adbc`\n- When working on telemetry/tracing: `.agents/telemetry-tracing.md`\n- When working on dbt-docs-server (static site + DuckDB-WASM in the browser): `.agents/dbt-docs-server.md`\n- Always check for nested `AGENTS.md` files in subdirectories you modify\n- If context is not enough, try reading repo overview / architecture as last resort: `README.md`\n"},"files":{"AGENTS.md":"# Project Instructions (AI Agents)\n\nThese instructions are for coding agents (Codex CLI, Claude Code, etc).\n\nPaths in this file and in `.agents/` are relative to the directory containing this file.\n\n## Hard Rules\n\n### Code Style\n\n- Follow existing code style and patterns in the given crate/module.\n- Keep changes minimal and focused to the task at hand.\n- Prefer simple, readable code over clever or complex solutions.\n\n### Changelog\n\n- Never manually create or write changelog YAML files. Always use `changie new` to generate entries.\n- Run `changie new` from the repository root with flags: `changie new --kind \"<kind>\" --body \"<description>\" --custom \"project=<project>\" --custom \"issue=<number>\" --custom \"author=<handle>\" --interactive=false`\n- For optional empty fields (`issue`, `author`), prompt the user if running locally or pass a space (e.g., `--custom \"issue= \"`) then edit the generated file to replace `' '` with `\"\"`.\n\n### Running dev commands\n\n- Never run blanket `cargo` commands without `-p <crate>` unless explicitly asked.\n- Avoid context pollution: don’t paste long logs; prefer LLM-friendly JSONL output and short excerpts.\n- Avoid full builds and full test runs during iteration; keep commands scoped and fast.\n\n## Where To Look Next (Task-Specific)\n\n- Respect author preferences (optional/local): `AGENTS.local.md`\n- When working on Adapters: `.agents/adapters.md`. Adapters consist of the following crates:\n  - `dbt-adapter`\n  - `dbt-adapter-core`\n  - `dbt-adapter-sql`\n  - `dbt-auth`\n  - `dbt-sql-keywords`\n  - `dbt-adbc`\n- When working on telemetry/tracing: `.agents/telemetry-tracing.md`\n- When working on dbt-docs-server (static site + DuckDB-WASM in the browser): `.agents/dbt-docs-server.md`\n- Always check for nested `AGENTS.md` files in subdirectories you modify\n- If context is not enough, try reading repo overview / architecture as last resort: `README.md`\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# Project Instructions (AI Agents)\n\nThese instructions are for coding agents (Codex CLI, Claude Code, etc).\n\nPaths in this file and in `.agents/` are relative to the directory containing this file.\n\n## Hard Rules\n\n### Code Style\n\n- Follow existing code style and patterns in the given crate/module.\n- Keep changes minimal and focused to the task at hand.\n- Prefer simple, readable code over clever or complex solutions.\n\n### Changelog\n\n- Never manually create or write changelog YAML files. Always use `changie new` to generate entries.\n- Run `changie new` from the repository root with flags: `changie new --kind \"<kind>\" --body \"<description>\" --custom \"project=<project>\" --custom \"issue=<number>\" --custom \"author=<handle>\" --interactive=false`\n- For optional empty fields (`issue`, `author`), prompt the user if running locally or pass a space (e.g., `--custom \"issue= \"`) then edit the generated file to replace `' '` with `\"\"`.\n\n### Running dev commands\n\n- Never run blanket `cargo` commands without `-p <crate>` unless explicitly asked.\n- Avoid context pollution: don’t paste long logs; prefer LLM-friendly JSONL output and short excerpts.\n- Avoid full builds and full test runs during iteration; keep commands scoped and fast.\n\n## Where To Look Next (Task-Specific)\n\n- Respect author preferences (optional/local): `AGENTS.local.md`\n- When working on Adapters: `.agents/adapters.md`. Adapters consist of the following crates:\n  - `dbt-adapter`\n  - `dbt-adapter-core`\n  - `dbt-adapter-sql`\n  - `dbt-auth`\n  - `dbt-sql-keywords`\n  - `dbt-adbc`\n- When working on telemetry/tracing: `.agents/telemetry-tracing.md`\n- When working on dbt-docs-server (static site + DuckDB-WASM in the browser): `.agents/dbt-docs-server.md`\n- Always check for nested `AGENTS.md` files in subdirectories you modify\n- If context is not enough, try reading repo overview / architecture as last resort: `README.md`\n","category":"root","tokens":474}]}