description if e get
### Review Process
- PRs go through maintainer and community review
- Educational clarity dey important
- Code examples suppose follow current best practices
- Translations go through accuracy and cultural
angkop
### Proseso ng Review
- Ang mga PR ay sinusuri ng mga maintainer at komunidad
- Pinapahalagahan ang kalinawan sa edukasyon
- Dapat sundin ng mga halimbawa ng code ang kasalukuyang best practices
issue-first rule for non-trivial features; `docs/code-review-guidelines.md` is the reviewer-facing complement.
## Codereview guide
- Use `docs/code-review-guidelines.md` as the repository-wide review standard. That document is the operational guide
cross-workflow behavior, update the topology tests instead of relying only on workflow YAML review.
## Architecture
GitHub automation uses two layers.
Business layer:
- Business workflows decide what happened and what
server
spec. Fallback backends must be reported honestly. MCP guidance, diagnostics,
and reviewed-memory search are read-only. Cargo verification is CLI-only and
is not exposed through MCP. Host
build.sh --test`; that is expected, not an external service.
## Working Rules
- When reviewing documentation or code, inspect the full affected path and report all verifiable findings in one review
screenshots of the changed UI in its GitHub description before it is ready for review. This applies to new PRs and updates to existing PRs.
- Capture and inspect the rendered
system, test layout.
- **[frontend/AGENTS.md](frontend/AGENTS.md)** — frontend depth: Next.js App Router layout,
thread/streaming data flow, code style, commands.
## What is DeerFlow
DeerFlow is a LangGraph-based AI super-agent system with
uses `[...value.trim()].length`, matching Pydantic;
do not use HTML `maxLength`, which counts UTF-16 code units instead.
- **Imports**: Enforced ordering (builtin → external → internal → parent → sibling), alphabetized, newlines between groups
later changes after
it is part of the trusted base. Preapproved digests must be code-reviewed in
that first change; after the corresponding file revision lands, promote the
consumed digest
components, hooks, helpers, or types). Smaller, focused files are friendly to humans and agents.
### CodeReview
Before reviewing a PR / diff / branch change, read the **deep-review** skill. Ordinary review
enforces
# Writing Pull Requests
Fill in [`.github/pull_request_template.md`](./.github/pull_request_template.md), written for a reviewer who has never seen this code:
- No jargon — plain language, no internal shorthand.
- The before and after
default` for throwing an exception for unexpected values, or an assertion error if this code branch is unreachable.
## Types, Generics, and Suppressions
- Prefer type-safe constructs; avoid raw types
part workflows. Store secrets in environment variables such as `OPENAI_API_KEY`; never hard-code keys inside notebooks.
## Testing Guidelines
Execute notebooks top-to-bottom after installing dependencies and clear
Notebooks should execute without errors
- README files should be clear and accurate
- Follow existing code patterns in the repository
- Maintain consistency with other lessons
## Additional Notes
### Common Gotchas
1. **Python