references
- Mga Larawan: I-imbak sa `/images/` directory, gumamit ng deskriptibong alt text
- Mga Code Blocks: Gumamit ng triple backticks na may language identifier kung naaangkop
### Mga Alituntunin sa Nilalaman
search.
- When the user asks to fix tests, fix the tests - not the source code - unless explicitly asked otherwise.
- If you're working with directories or files, utilise the functions
video, say so explicitly and explain why, and include the exact commands/steps for the reviewer to reproduce.
## Validate Every Experience
Almost everything we change has an effect on the outside
calls, and be documented in the skill.
- Review skills and scripts for safety before sharing or running.
- Do not delete existing Claude Code marketplace files such as `.claude-plugin/marketplace.json
context` for direct API context preflight and `$autoreview` for isolated reviews; preserve its reviewer isolation.
- Claude Code parallel/background work (Codex workers, monitors, long jobs): each = own harness-tracked task
whether to take another action.
1. **Review:** When the task is complete, you review the response, code changes, and validation results.
The repeated reasoning, action, and validation steps form
accommodate new violations.
### Code structure and readability
Apply these rules when writing or reviewingcode. The
[CodeReview Style Guide](https://github.com/zhaochenyang20/sglang-diffusion-routing/issues/32)
is a reference; the rules here take
errors from outdated dependencies; upgrade the dependency instead
- Always ask before removing functionality or code that appears to be intentional
- Do not add fallback behavior by default. If required context
OpenCode's contract:
- `deny` → `throw new Error(...)` from the hook
- `review` → annotate `output.args.__agt_review_reason`
- `allow` → return undefined
- exposes `agt_policy_status` and `agt_policy_check_text` as both
surfaces meant for direct external consumption |
| Python runtime and product code | `*/` | Runtime code, applications, policy engines, trust, SRE, compliance, and other Python product surfaces that have not moved into
discoverability at least once.
- Security-sensitive changes should review `docs/security/` and `docs/security/threat-model.md`.
## Validation
- Check that links, file paths, and fenced code blocks are valid.
- Keep headings and page titles stable
Multi-platform support (Windows, Linux, macOS, containers)
## General
* Make only high confidence suggestions when reviewingcode changes.
* Always use the latest version C#, currently C# 13 features.
* Never change global.json
contradictions require rule repair plus negative or mutation coverage.
- Characterize before moving code. For status, quota, review-packet, scheduler,
monitor, and handoff behavior, add or extend parity fixtures first, then
AGENTS.md
This file provides guidance to AI coding agents working with code in this repository.
CLAUDE.md is a symlink to this file — they are the same file, do not update