Skip to content

Conversation

@matthewshaver
Copy link
Contributor

What are you changing in this pull request and why?

Adds an AGENTS.md file

Checklist

@matthewshaver matthewshaver requested a review from a team as a code owner November 4, 2025 16:37
@vercel
Copy link

vercel bot commented Nov 4, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
docs-getdbt-com Ready Ready Preview Nov 20, 2025 8:16pm

@github-actions github-actions bot added the Docs team Authored by the Docs team @dbt Labs label Nov 4, 2025
@mirnawong1 mirnawong1 mentioned this pull request Nov 4, 2025
5 tasks

#### When to Use Code Font
Use backticks for:
- Source code (SQL, YAML, JavaScript)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Source code (SQL, YAML, JavaScript)
- Source code (SQL, YAML, JavaScript, JSON, Python, Jinja)


This guide provides AI agents with essential rules and patterns for making editorial changes to the dbt documentation repository. These guidelines are derived from the [content style guide](contributing/content-style-guide.md).

## Quick Reference
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is this section for?

- Orchestrator
- Semantic Layer
- Copilot

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Tone and clarity
- Use active voice, avoid passive voice.
- Write in a friendly but professional tone.
- Keep sentences short (ideally under 20 words).
- Prefer plain English over jargon.
- Avoid unnecessary qualifiers (just, simply, easily).

- Copilot

### Text Formatting

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#### Headings
- Use sentence case for all headings.
- Use `##` for section headings within a page; avoid `#`.
- Do not end headings with punctuation.

- Copilot

### Text Formatting

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok i see its a intro section

Suggested change
Use consistent Markdown formatting to improve readability, accessibility, and editorial quality. Formatting should reflect context—not just visual style.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Docs team Authored by the Docs team @dbt Labs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants