docs/`; localized docs live in `docs_zh-CN/` and `docs/vietnamese/`. Maintenance scripts and tests are in `tools/scripts/` and `tools/scripts/tests/`. The hosted catalog app is in `apps/web-app/`. Registry outputs such
reject what is obsolete in a reply
that says why. After each round: focused tests, `npx tsc --noEmit` in every workspace you changed,
push, then request the next review naming
Prefix the full relative path, or source the activate script:
```bash
cd /path/to/sentry && .venv/bin/pytest tests/...
cd /path/to/sentry && source .venv/bin/activate && pytest tests/...
```
For AI agents: always use `required_permissions
Frontend Development Guide
> For critical commands and testing rules, see the "Command Execution Guide" section in `/AGENTS.md` in the repository root.
## Frontend Tech Stack
- **Language**: TypeScript
- **Framework**: React 19
- **Build
Python Testing Guide
> For test commands (`make test-selective`, `pytest`), see the "Command Execution Guide" section in `/AGENTS.md` in the repository root.
>
> This guide covers Python tests. For frontend React/TypeScript
Reference other files with relative paths from the
skill root, kept one level deep.
**Tests never live under `skills/`.** A skill directory ships only what an agent loads. Checks
Commands
Prefix dev servers and migration commands with `dotenvx run -f .env.local --`. Tests, typechecks, linters, boundary checks, and `pnpm build` do not need it; if one fails on a missing
tool, add one or document why it is intentionally omitted. Add or update tests that prove the CLI and MCP surfaces remain aligned.
In the `docs/src/app/` MDX files, always
pull request:
- `make format` – run code formatters
- `make lint` – run the linter
- `make test` – execute the test suite
To run a particular test file or to pass additional pytest options
list records each exemption's reason and the removal conditions for temporary translation exemptions.
## Testing
- Run unit tests with `make test`, not `go test` directly.
- `make test` sets
both background-workspace and active-pane
cardinality when applicable.
Prefer deterministic operation or architecture tests to wall-clock CI limits.
Performance benchmarks are supporting evidence, not substitutes for behavioral
coverage
current code. Follow their path and symbol references, then verify the relevant implementation, tests, migrations, and recent history. Treat sections labeled **Inference** as hypotheses; never silently promote them to fact
covered in the root `AGENTS.md` — this file covers conventions and App Builder architecture.
## Testing context
Before adding or changing tests for `src/AppBuilder/**`, read
`src/test/app-builder/README.md` for public seams and
`ee/.agents/skills/app-builder-widget-tdd/SKILL.md
Strong typing always. Never `any` — use precise types, or cast through `unknown` where unavoidable (test private access, caught errors).
- *A Philosophy of Software Design*, pragmatically: deep modules (simple interface hiding
logic |
| `crates/openhuman-cli/` | The `openhuman-core` binary (`src/main.rs`), the developer/benchmark bins (`src/bin/`), and every root `tests/*.rs` / `examples/*.rs` target; depends on `openhuman-tinyhumans` for the backend transport the core does
harness outputs
make garden # drift detection (dead links, stale artifacts, oversize skills)
make test # full pytest suite (plugin-eval + tools/tests/)
make smoke-test # real-CLI subprocess tests against generated artifacts
commands fail
- Never use `flox activate` in interactive sessions (it hangs if you try)
- Tests:
- Universal: `hogli test ` — auto-detects test type (Python, Jest, Playwright, Rust, Go)
- Single test: `hogli