@devries-cameron20 / composio-1 / commits / 7c88f71a7
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

docs: clarify contribution policy for issues, PRs, and docs links (#4602)

This PR: - adds a **Contribution Policy** to `CONTRIBUTING.md`: Composio employees can open issues and PRs; external contributors open an issue first and submit PRs only for an existing, open issue - states that we may close PRs that don't meaningfully improve the SDKs, CLI, or docs, and that authors must read every line they submit, including LLM-assisted code - restricts docs links to third-party projects to frontier model providers, frameworks and platforms Composio provider packages support (LangChain, Vercel AI SDK, Google Vertex AI), and Composio partners, and routes partnership requests to https://composio.dev/contact - mirrors these rules in `AGENTS.md`, `docs/AGENTS.md`, `docs/CONTRIBUTING.md`, and the PR template so agents and contributors see them - tightens the rest of `CONTRIBUTING.md` and fixes stale references (`docs/CLAUDE.md` → `docs/CONTRIBUTING.md`, ISC → MIT to match `LICENSE`) Verified with `pnpm validate:agent-skills` and `pnpm validate:skill-routing`.

Alberto Schiabel committed Sep 24, 2026 at 11:20 UTC 7c88f71a7affd62112f7d33fba3da2e0bce3490c
5 files changed +151 -170
.github/PULL_REQUEST_TEMPLATE.md
+7 -1
@@ -1,5 +1,9 @@
1 ## Summary
2 -Explain the motivation and context for this change. Link to any related issues.
2 +Explain the motivation and context for this change.
3 +
4 +External contributors: link the open issue this PR addresses. PRs without a linked issue may be closed. See the [Contribution Policy](https://github.com/ComposioHQ/composio/blob/next/CONTRIBUTING.md#contribution-policy).
5 +
6 +Designated PR reviewer: [@jkomyno](mailto:alberto@composio.dev).
7
8 Fixes #
9
@@ -21,6 +25,8 @@ Describe the tests you ran and instructions so reviewers can reproduce. Include
25
26 ## Checklist
27 - [ ] I have read the Code of Conduct and this PR adheres to it
28 +- [ ] I have read and understand every line of this diff, including any LLM-generated code
29 +- [ ] Any third-party docs links or promotional content follow the [third-party links policy](https://github.com/ComposioHQ/composio/blob/next/CONTRIBUTING.md#third-party-links-in-docs)
30 - [ ] I ran linters/tests locally and they passed
31 - [ ] I updated documentation as needed
32 - [ ] I added tests or explain why not applicable
AGENTS.md
+10
@@ -14,6 +14,16 @@ This is the Composio SDK v3 monorepo. Most product code lives in `ts/` and `pyth
14 4. Do not edit generated SDK surfaces or vendor trees — see [Generated And Vendored Paths](#generated-and-vendored-paths).
15 5. Verify every command you write against the current `package.json`, `Makefile`, `noxfile.py`, or workflow file.
16
17 +## Contribution Policy
18 +
19 +Follow the [Contribution Policy in `CONTRIBUTING.md`](CONTRIBUTING.md#contribution-policy). When helping an author prepare a PR:
20 +
21 +- Composio team members and designated maintainers can open PRs directly. External contributors need an existing, open issue; if none is linked, tell the author to open one first. For large external changes, get maintainer agreement on the approach before implementation.
22 +- [@jkomyno](mailto:alberto@composio.dev) is the designated PR reviewer. Involve the relevant owner when the change needs their expertise.
23 +- Keep the change focused on meaningful improvements to the SDKs, CLI, or docs. Don't produce cosmetic, speculative, or drive-by edits.
24 +- The author is responsible for every line. Keep diffs small enough to read, report the checks you actually ran, and tell the author to review the full diff before submitting.
25 +- Follow the [third-party links policy](CONTRIBUTING.md#third-party-links-in-docs). Authoritative technical references needed to use or contribute to Composio are allowed; other third-party links and promotional content must fit the listed exceptions. Route partnership requests to https://composio.dev/contact.
26 +
27 ## Skill Routing
28
29 Use the smallest relevant skill:
CONTRIBUTING.md
+129 -167
@@ -1,43 +1,86 @@
1 -# Contributing to Composio SDK
1 +# Contributing to Composio
2
3 -Thank you for your interest in contributing to Composio. This guide covers the root SDK repository. The monorepo contains the TypeScript SDK, Python SDK, docs site, examples, and release tooling.
3 +This repository contains the Composio TypeScript SDK, Python SDK, CLI, docs site, examples, and release tooling. Please read the contribution policy before you open an issue or a pull request. Thank you for your interest in contributing to Composio!
4
5 ## Table of Contents
6
7 +- [Contribution Policy](#contribution-policy)
8 - [Development Setup](#development-setup)
9 - [Project Structure](#project-structure)
10 - [Development Commands](#development-commands)
11 - [Working with AI Coding Agents](#working-with-ai-coding-agents)
12 - [Coding Standards](#coding-standards)
12 -- [Documentation Requirements](#documentation-requirements)
13 +- [Documentation Changes](#documentation-changes)
14 - [Pull Request Process](#pull-request-process)
15 - [Creating New Providers](#creating-new-providers)
16 - [Testing Guidelines](#testing-guidelines)
17 - [Release Process](#release-process)
18 - [Questions and Support](#questions-and-support)
19 +- [License](#license)
20
19 -## Development Setup
21 +## Contribution Policy
22
21 -### Prerequisites
23 +### Open an issue first
24 +
25 +Issues are the preferred way to contribute. A clear bug report or feature request is often more useful to us than a pull request, and it avoids long review cycles for changes we might not accept.
26 +
27 +- **Composio team members and designated maintainers** can open issues and pull requests directly.
28 +- **External contributors** should open an issue first. Open a pull request only for an existing, open issue, and link that issue in the pull request description. For large changes, wait for a maintainer to confirm the approach on the issue before you start implementation. Small fixes do not require prior maintainer approval.
29 +
30 +Use the [issue templates](https://github.com/ComposioHQ/composio/issues/new/choose) for bug reports, feature requests, and tool requests. For support questions, see [Questions and Support](#questions-and-support). For security issues, follow [`SECURITY.md`](.github/SECURITY.md) instead of opening a public issue.
31 +
32 +### PR reviewer
33 +
34 +[@jkomyno](mailto:alberto@composio.dev) is the designated reviewer for pull requests. Involve the relevant SDK, CLI, or docs owner when the change needs their expertise.
35 +
36 +### Pull requests we may close
37 +
38 +We reserve the right to close pull requests that don't make a meaningful contribution to Composio's SDKs, CLI, or docs. This includes pull requests that:
39 +
40 +- have no linked issue, when opened by an external contributor
41 +- make cosmetic, speculative, or drive-by changes without a clear user benefit
42 +- are too broad to review, or mix unrelated changes
43 +- add third-party links or promotional content outside the [third-party links policy](#third-party-links-in-docs)
44 +- show that the author hasn't read or verified the submitted code
45 +
46 +### Read the code you submit
47 +
48 +You are responsible for every line in your pull request, whether you wrote it yourself or with an LLM or coding agent. Before you open a pull request:
49 +
50 +- Read and understand the whole diff.
51 +- Run the relevant checks and describe what you ran.
52 +- Remove unrelated edits, generated noise, and speculative code.
53 +- Be ready to explain any change a reviewer asks about.
54 +
55 +AI assistance is welcome. Unreviewed AI output is not.
56 +
57 +### Third-party links in docs
58 +
59 +You can link to authoritative technical documentation needed to use or contribute to Composio, including toolkit setup instructions, OAuth documentation, and language or runtime references.
60 +
61 +Other third-party links and promotional content are limited to:
62 +
63 +- frontier model providers, such as OpenAI and Anthropic
64 +- frameworks and platforms that Composio provider packages support, such as LangChain, the Vercel AI SDK, and Google Vertex AI
65 +- partners that have an agreement with Composio
66 +
67 +### Partnerships
68
23 -Tool versions are pinned in [`mise.toml`](mise.toml), which is the source of truth for local development and CI:
69 +To propose a partnership, including a docs listing or integration, contact us through [composio.dev/contact](https://composio.dev/contact). Don't open an issue or a pull request for a partnership request.
70
25 -- Node.js 24.17.0
26 -- pnpm 11.8.0
27 -- Bun 1.3.10
28 -- Deno 2.6.7
29 -- Python 3.12
30 -- uv 0.8.19
71 +## Development Setup
72 +
73 +### Prerequisites
74
32 -Use [mise](https://mise.jdx.dev) to install the toolchain:
75 +Tool versions are pinned in [`mise.toml`](mise.toml), which is the source of truth for local development and CI. It pins Node.js, pnpm, Bun, Deno, Python, and uv. Install the toolchain with [mise](https://mise.jdx.dev):
76
77 ```bash
78 mise install
79 ```
80
38 -mise installs pnpm through its npm backend. Do not rely on Corepack for this repository.
81 +mise installs pnpm through its npm backend. Don't rely on Corepack for this repository.
82
40 -### Getting Started
83 +### Getting started
84
85 1. Fork and clone the repository:
86
@@ -46,27 +89,12 @@ mise installs pnpm through its npm backend. Do not rely on Corepack for this rep
89 cd composio
90 ```
91
49 -2. Install the pinned toolchain:
92 +2. Install the toolchain and dependencies, then build and test:
93
94 ```bash
95 mise install
53 - ```
54 -
55 -3. Install dependencies:
56 -
57 - ```bash
96 pnpm install
59 - ```
60 -
61 -4. Build the project:
62 -
63 - ```bash
97 pnpm build
65 - ```
66 -
67 -5. Run tests:
68 -
69 - ```bash
98 pnpm test
99 ```
100
@@ -97,64 +125,46 @@ composio/
125 └── .github/ # GitHub Actions and shared CI actions
126 ```
127
128 +Don't hand-edit generated or vendored paths, such as `ts/vendor/**`, `ts/packages/core/generated/**`, and lockfiles. [`AGENTS.md`](AGENTS.md#generated-and-vendored-paths) has the full list.
129 +
130 ## Development Commands
131
132 ```bash
103 -# Build all packages
104 -pnpm build
105 -
106 -# Build TypeScript packages only
107 -pnpm build:packages
108 -
109 -# Lint TypeScript packages
110 -pnpm lint
111 -
112 -# Fix lint issues where possible
113 -pnpm lint:fix
114 -
115 -# Format supported files
116 -pnpm format
117 -
118 -# Create a new TypeScript provider
119 -pnpm create:provider <provider-name> [--agentic]
120 -
121 -# Create a new TypeScript example
122 -pnpm create:example <example-name>
123 -
124 -# Check peer dependencies
125 -pnpm check:peer-deps
126 -
127 -# Update peer dependencies
128 -pnpm update:peer-deps
133 +pnpm build # Build all packages
134 +pnpm build:packages # Build TypeScript packages only
135 +pnpm lint # Lint TypeScript packages
136 +pnpm lint:fix # Fix lint issues where possible
137 +pnpm format # Format supported files
138 +pnpm typecheck # Type-check TypeScript packages
139 +pnpm check:peer-deps # Check peer dependencies
140 +pnpm update:peer-deps # Update peer dependencies
141 +
142 +pnpm create:provider <provider-name> [--agentic] # New TypeScript provider
143 +pnpm create:example <example-name> # New TypeScript example
144 ```
145
146 ### Dead code detection
147
133 -The `Dead Code` CI workflow reports likely-orphaned code on every PR (findings
134 -land in the run's Step Summary; it never fails the build). Run the same checks
135 -locally:
148 +The `Dead Code` CI workflow reports likely-orphaned code on every PR. Findings land in the run's Step Summary and never fail the build. Run the same checks locally:
149
150 ```bash
138 -# TypeScript — unused files, exports, types and dependencies
151 +# TypeScript: unused files, exports, types, and dependencies
152 pnpm dlx knip@5 # config in knip.json
153
141 -# Python — unused functions, classes and variables
154 +# Python: unused functions, classes, and variables
155 cd python && make dead-code # vulture; allowlist in python/config/vulture_allowlist.py
156
144 -# GitHub Actions — orphaned reusable workflows and composite actions
157 +# GitHub Actions: orphaned reusable workflows and composite actions
158 bash .github/scripts/check-orphan-ci.sh
159 ```
160
148 -These tools carry false positives (public API surface, dynamic imports,
149 -import-map targets), so treat their output as advisory: verify a finding is
150 -truly unreferenced before deleting, and suppress confirmed false positives via
151 -`knip.json` / `vulture_allowlist.py`.
161 +These tools report false positives for public API surface, dynamic imports, and import-map targets. Verify that a finding is unreferenced before you delete it, and suppress confirmed false positives in `knip.json` or `vulture_allowlist.py`.
162
163 ## Working with AI Coding Agents
164
155 -This repository ships its own agent guidance, and CI keeps it honest. You get it for free — an agent that reads this repo inherits the layout, commands, and guardrails without setup.
165 +This repository ships its own agent guidance, and CI keeps it accurate. An agent that reads this repository inherits its layout, commands, and rules, including the [Contribution Policy](#contribution-policy).
166
157 -`AGENTS.md` files live at the root and inside each subtree (`ts/`, `python/`, `docs/`, and the packages). Coding agents read the nearest one automatically, so you usually do not need to do anything beyond keeping them accurate when you move code. The canonical skill tree is `.agents/skills/` (with `.claude/skills` as a compatibility symlink): focused, task-scoped skills that route an agent to the right workflow, from `bug-fixing` to `cli-release`.
167 +`AGENTS.md` files live at the root and inside each subtree (`ts/`, `python/`, `docs/`, and the packages). Coding agents read the nearest one automatically. Keep them accurate when you move code. The canonical skill tree is `.agents/skills/`, with `.claude/skills` as a compatibility symlink.
168
169 Two deterministic checks guard this guidance:
170
@@ -163,65 +173,58 @@ pnpm validate:agent-skills # frontmatter, reference links, stale guidance ref
173 pnpm validate:skill-routing # routing smoke test over skill descriptions
174 ```
175
166 -`validate:agent-skills` parses `package.json`, `python/Makefile`, and `python/noxfile.py`, then verifies every command mentioned in guidance actually exists — so guidance cannot recommend a command that was renamed away. Both checks run in CI via `.github/workflows/agent-substrate.yml` whenever agent guidance changes.
176 +`validate:agent-skills` parses `package.json`, `python/Makefile`, and `python/noxfile.py`, then verifies that every command mentioned in guidance exists. Both checks run in CI through `.github/workflows/agent-substrate.yml`.
177
168 -If you add or rename a skill, or rewrite a skill description, run both checks and add a routing probe in `ts/scripts/test-skill-routing.mjs` so routing stays covered. To author or edit a skill, read [`.agents/skills/skill-maintenance/SKILL.md`](.agents/skills/skill-maintenance/SKILL.md) first.
178 +If you add or rename a skill, or rewrite a skill description, run both checks and add a routing probe in `ts/scripts/test-skill-routing.mjs`. Read [`.agents/skills/skill-maintenance/SKILL.md`](.agents/skills/skill-maintenance/SKILL.md) before you author or edit a skill.
179 +
180 +Using an agent doesn't change your responsibility: [read the code you submit](#read-the-code-you-submit).
181
182 ## Coding Standards
183
184 ### TypeScript
185
174 -1. Follow the style of the package you are editing.
175 -2. Use TypeScript for new TypeScript SDK code.
176 -3. Use named exports for public APIs unless the local package pattern says otherwise.
177 -4. Keep public API changes typed and documented with TSDoc.
178 -5. Add focused tests for new behavior and bug fixes.
179 -6. Use Oxlint and Prettier through the repo scripts.
180 -7. Keep generated or vendored code out of manual edits unless the package explicitly owns that output.
186 +- Follow the style of the package you're editing.
187 +- Use named exports for public APIs unless the package uses another pattern.
188 +- Type public API changes and document them with TSDoc.
189 +- Add focused tests for new behavior and bug fixes.
190 +- Use Oxlint and Prettier through the repository scripts.
191
192 ### Python
193
184 -1. Follow the existing Python SDK layout under `python/`.
185 -2. Use Ruff formatting and linting through the Python make targets.
186 -3. Keep provider-specific changes inside the relevant `python/providers/*` package.
187 -4. Add pytest coverage for behavior changes.
194 +- Follow the existing layout under `python/`.
195 +- Use Ruff formatting and linting through the Python make targets.
196 +- Keep provider-specific changes inside the relevant `python/providers/*` package.
197 +- Add pytest coverage for behavior changes.
198
189 -### Error Handling
199 +### Error handling
200
191 -1. Use the existing error classes and result shapes in the package you are editing.
192 -2. Include enough context in error messages to identify the failing operation.
193 -3. Avoid swallowing errors unless the caller has an explicit fallback path.
201 +- Use the existing error classes and result shapes in the package you're editing.
202 +- Include enough context in error messages to identify the failing operation.
203 +- Don't swallow errors unless the caller has an explicit fallback path.
204
195 -## Documentation Requirements
205 +## Documentation Changes
206
207 Update docs when a change affects public behavior, install flows, examples, environment variables, release steps, or provider usage.
208
199 -For documentation-site work, read [`docs/CLAUDE.md`](docs/CLAUDE.md) first. It documents the docs app, MDX conventions, link checking, generated data, and docs branch workflow.
200 -
201 -Package documentation should generally include:
209 +For the documentation site, read [`docs/CONTRIBUTING.md`](docs/CONTRIBUTING.md) and [`docs/AGENTS.md`](docs/AGENTS.md). They cover the docs app, MDX conventions, link checks, generated data, and validation.
210
203 -1. A short package description.
204 -2. Installation instructions.
205 -3. Usage examples.
206 -4. Public API notes.
207 -5. Environment variables or authentication requirements when relevant.
208 -6. Provider limitations or streaming details when relevant.
211 +Docs changes follow the [third-party links policy](#third-party-links-in-docs).
212
213 ## Pull Request Process
214
212 -1. Create a branch from the target base branch. Most active SDK and docs work targets `next`.
215 +1. For external contributions, confirm that an open issue exists. For large changes, get maintainer agreement on the approach before you start implementation.
216 +
217 +2. Branch from `next`, which is the base for most SDK and docs work:
218
219 ```bash
220 git checkout next
221 git pull origin next
217 - git checkout -b feature/your-feature-name
222 + git checkout -b feat/your-change
223 ```
224
220 -2. Make focused changes that match the issue or feature scope.
225 +3. Keep the change focused on the issue. Split unrelated changes into separate pull requests.
226
222 -3. Add or update tests for behavior changes.
223 -
224 -4. Update documentation when user-facing behavior changes.
227 +4. Add or update tests for behavior changes, and update docs for user-facing changes.
228
229 5. Add a changeset for changes that affect published TypeScript packages:
230
@@ -229,43 +232,32 @@ Package documentation should generally include:
232 pnpm changeset
233 ```
234
232 - Root-level documentation-only changes, such as edits to this file, do not need a changeset.
235 + Documentation-only and agent-guidance-only changes don't need a changeset.
236
234 -6. Run the smallest meaningful verification command locally before opening the PR.
237 +6. Read your full diff and run the smallest meaningful checks locally.
238
236 -7. Push your branch and open a PR against the correct base branch.
239 +7. Open a pull request against `next`. Fill in the template, link the issue for external contributions (or when one exists for team contributions), and describe how you tested the change. Request review from [@jkomyno](mailto:alberto@composio.dev).
240
241 ## Creating New Providers
242
240 -### TypeScript Providers
243 +For external contributions, open an issue before you build a new provider. Get maintainer agreement before implementing large changes. We may decline providers we can't maintain.
244
242 -Use the TypeScript provider creation script:
245 +### TypeScript providers
246
247 ```bash
248 pnpm create:provider my-provider [--agentic]
249 ```
250
248 -Then:
249 -
250 -1. Implement the required provider methods.
251 -2. Add tests under the provider package.
252 -3. Add examples or docs when the provider has user-facing setup details.
253 -4. Run the package tests and relevant build checks.
251 +Implement the required provider methods, add tests under the provider package, and add docs or examples for user-facing setup.
252
255 -### Python Providers
253 +### Python providers
254
257 -Use the Python provider creation target from the `python/` directory:
255 +Run from the `python/` directory:
256
257 ```bash
258 cd python
259 make create-provider name=my-provider
262 -```
263 -
264 -For agentic providers:
265 -
266 -```bash
267 -cd python
268 -make create-provider name=my-provider agentic=true
260 +make create-provider name=my-provider agentic=true # agentic provider
261 ```
262
263 Then add provider tests and run the relevant Python checks.
@@ -274,61 +266,37 @@ Then add provider tests and run the relevant Python checks.
266
267 ### TypeScript SDK
268
277 -Run the root TypeScript test suite:
278 -
269 ```bash
280 -pnpm test
281 -```
282 -
283 -Run all TypeScript end-to-end tests:
284 -
285 -```bash
286 -pnpm test:e2e
287 -```
288 -
289 -Run runtime-specific end-to-end tests:
290 -
291 -```bash
292 -pnpm test:e2e:node
270 +pnpm test # Unit tests
271 +pnpm test:e2e # All end-to-end tests
272 +pnpm test:e2e:node # Runtime-specific end-to-end tests
273 pnpm test:e2e:deno
274 pnpm test:e2e:cli
275 pnpm test:e2e:cloudflare
296 -```
297 -
298 -Open the Vitest UI:
299 -
300 -```bash
301 -pnpm test:ui
276 +pnpm test:ui # Vitest UI
277 ```
278
279 ### Python SDK
280
306 -Set up the Python development environment:
307 -
281 ```bash
282 cd python
283 make env
284 source .venv/bin/activate
312 -```
313 -
314 -Run Python checks:
315 -
316 -```bash
285 make fmt
286 make chk
287 make tst
288 make snt
289 ```
290
323 -You can also run a focused pytest command through uv:
291 +For a focused run, use pytest through uv:
292
293 ```bash
294 uv run pytest tests/test_sdk.py -v
295 ```
296
329 -### Docs Site
297 +### Docs site
298
331 -For docs changes:
299 +Run from `docs/`:
300
301 ```bash
302 cd docs
@@ -337,28 +305,22 @@ bun run build
305 bun run lint:links
306 ```
307
340 -See [`docs/CLAUDE.md`](docs/CLAUDE.md) for the full docs workflow.
308 +[`docs/CONTRIBUTING.md`](docs/CONTRIBUTING.md) lists the full set of docs checks.
309
310 ## Release Process
311
312 Only maintainers publish releases.
313
346 -For TypeScript package and CLI release details, use [`ts/docs/internal/release.md`](ts/docs/internal/release.md). The root scripts are:
347 -
348 -```bash
349 -pnpm changeset
350 -pnpm changeset:version
351 -pnpm changeset:release
352 -```
353 -
354 -For Python package release details, use [`python/docs/release.md`](python/docs/release.md). Python package versioning and release preparation are handled from the `python/` workspace.
314 +- TypeScript packages and the CLI: [`ts/docs/internal/release.md`](ts/docs/internal/release.md)
315 +- Python packages: [`python/docs/release.md`](python/docs/release.md)
316
317 ## Questions and Support
318
358 -- Join our [Discord Community](https://discord.gg/composio)
359 -- Check our [Documentation](https://docs.composio.dev)
360 -- File issues on [GitHub](https://github.com/ComposioHQ/composio/issues)
319 +- [Documentation](https://docs.composio.dev)
320 +- [Discord community](https://discord.gg/composio)
321 +- [Support guide](.github/SUPPORT.md)
322 +- Partnerships: [composio.dev/contact](https://composio.dev/contact)
323
324 ## License
325
364 -By contributing to Composio SDK, you agree that your contributions will be licensed under the ISC License.
326 +By contributing to Composio, you agree that your contributions are licensed under the [MIT License](LICENSE).
docs/AGENTS.md
+1
@@ -36,6 +36,7 @@ bun run generate:api-index
36
37 - TypeScript code blocks in MDX are checked during docs builds. Use `docs/agent-guidance/context/twoslash.md` before changing typed examples.
38 - Parse untyped or external data (JSON files, fetched payloads, framework page data) once at the boundary with zod schemas and let `z.infer` types flow downstream. Never hand-roll structural guards (`'x' in obj` / `typeof` chains), cast parsed JSON with `as`, or fake validation with `z.custom(() => true)`.
39 +- Follow the root [Contribution Policy](../CONTRIBUTING.md#contribution-policy), including its designated PR reviewer and [third-party links policy](../CONTRIBUTING.md#third-party-links-in-docs). Authoritative technical references needed to use or contribute to Composio are allowed; other third-party links and promotional content must fit the listed exceptions. Route partnership requests to https://composio.dev/contact.
40 - Internal docs links must be relative site paths such as `/docs/...`, `/reference/...`, or `/assets/...`.
41 - API reference pages and toolkit/meta-tool data are generated. Do not hand-edit generated data unless the local generator owns it.
42 - Changelog entries require `title` and `date` frontmatter, and dates use `YYYY-MM-DD`.
docs/CONTRIBUTING.md
+4 -2
@@ -1,6 +1,8 @@
1 # Change the Composio docs
2
3 -Use a pull request for a specific docs fix. Use a Developer Marketing issue in Linear with the Docs label when the work needs investigation, coordination, or a larger content plan. Link the issue and its source context in the PR so the reviewer can check the original problem.
3 +Use a pull request for a specific docs fix. For Composio team members, use a Developer Marketing issue in Linear with the Docs label when the work needs investigation, coordination, or a larger content plan. Link the issue and its source context in the PR so the reviewer can check the original problem.
4 +
5 +Composio team members and designated maintainers can open PRs directly. External contributors need an existing, open GitHub issue. For large external changes, get maintainer agreement on the approach before implementation. Read the root [Contribution Policy](../CONTRIBUTING.md#contribution-policy), including the [third-party links policy](../CONTRIBUTING.md#third-party-links-in-docs). Authoritative technical references needed to use or contribute to Composio are allowed. For a partnership request, contact us through [composio.dev/contact](https://composio.dev/contact).
6
7 For a runtime bug, include a reproducible example and involve the SDK or platform owner. A docs change cannot establish behavior that the product does not support.
8
@@ -58,6 +60,6 @@ The `Docs - Rebuild KB Semantic Artifact` workflow can rebuild it for eligible s
60
61 Describe the reader's problem, the resulting behavior, and the checks you ran. Include screenshots for visual changes and list checks that failed or could not run. Link the Linear issue when one exists. Docs-only changes do not need a Changeset.
62
61 -Request review from someone who can verify the changed topic. Involve the product owner for behavior, security, tenancy, or contractual claims. Follow the repository's review and merge requirements; a passing build alone does not verify those claims.
63 +Request review from [@jkomyno](mailto:alberto@composio.dev), the designated PR reviewer, and involve someone who can verify the changed topic. Involve the product owner for behavior, security, tenancy, or contractual claims. Follow the repository's review and merge requirements; a passing build alone does not verify those claims.
64
65 After merge, confirm the deployment succeeds and inspect the live page and `.md` representation. Check `Docs - Sync Algolia Search` for changes that affect retrieval. Update the linked issue with the published result once the change is verified. If the live result is wrong, report the affected URL and commit so the next fix starts from evidence.