Skip to content

docs: add coding agent guidance #81

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
longlho merged 1 commit into from
Jul 30, 2026
+26 −0
Merged

docs: add coding agent guidance #81

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
# Agent guidance

Follow [CONTRIBUTING.md](./CONTRIBUTING.md) for setup, development, and release
commands.

## Scope

- Treat `src/generated/`, `src/resources.ts`, and `src/resources/` as output
from a private SDK codegen pipeline. Do not edit them.
- Keep handwritten changes focused and preserve unrelated generated files.
- Update `package.json` and `pnpm-lock.yaml` together for dependency changes.

## Workflow

- Use Bazel targets instead of direct Node test or build commands.
- Run `bazel run //:gazelle` after adding files or changing imports.
- Do not bump versions, edit release PR output, or publish packages manually.

## Validation

- Run `bazel test //...`.
- Run `bazel test //:test //:package_checks //e2e:sdk_parity` for public-surface
changes.
- Run `pnpm lefthook run pre-commit --all-files --force --fail-on-changes`.
- Run live tests only when explicitly requested and `PPLX_API_TOKEN` is
available.