handoff; add focused `swift test --filter ...` runs for parser/provider fixes when possible.
- After any code change, run `make check` and fix all reported format/lint issues before handoff.
- Prefer CLI/focused tests
github/skills/). Load each skill whose description matches the
requested task, subsystem, or behavior.
For codereviews, follow the `/code-review` skill in addition to relevant domain skills and matching path-scoped
Pure code-agent PRs are not allowed: a human submitter must understand and be able to defend the change end-to-end.
- The submitting human is responsible for reviewing every
GitHub Copilot includes several agentic features that go beyond suggestion and conversation—they can reviewcode, take action on your behalf, and build applications. This card covers the following experiences
order.
- User-visible strings belong in `*.properties` for localization.
## Language
- Read [Code Style](./.agents/skills/code-style/SKILL.md) before writing or reviewing Kotlin or Java.
## Writing
Write every user-visible artifact in [ASD-STE100
Synchronization guidelines for Java/JNI (Android) and JavaScript/TypeScript (Web/WASM) when public C++ APIs change.
### 6. CodeReview & Invariant Auditing
* [skills/code_review/SKILL.md](skills/code_review/SKILL.md): Adversarial systems, concurrency, memory-model, and architecture codereview protocol
copy these)
- **DO NOT copy patterns from `packages/react/` (v8).** That's maintenance-only legacy code using runtime styling, class components, and different APIs.
- **DO NOT use `@fluentui/react` imports
ponytail** skill at level `full`. Load it before you
write, fix, refactor, or reviewcode, and before you add a dependency. Level switch:
`/ponytail lite|full|ultra`. Off: "stop ponytail
commit/CI gates cover them at the right time.
# Coding Guidelines
When generating or reviewingcode anywhere in this repo, always read [agent_docs/index.md](agent_docs/index.md) and follow/enforce those guidelines
fence, such as `{test="skip" lint="skip"}`, rather than adding tooling suppressions to pedagogical code. Examples that are linted are also type-checked with pyright; opt one out with `typecheck
edit from
outside the org is a supply-chain change rather than an ordinary codereview — a
maintainer carries legitimate ones forward in their own PR (#7024 is the case
implementation rename unless the migration of in-flight executions is
intentional and reviewed.
Resolve base and per-tool configuration with `OperationConfigRole` and `DurableOperationId`.
Handle known ID variants and retain
must equal `Hooks.on`'s attribute
names plus the host names. Drift fails CI, not codereview.
3. Fire it from exactly one place in the shell.
4. Document
make assertions about the HTTP requests if needed.
To assert what the code actually sent — headers included — take the `request_capture` fixture
instead. It reads the wire rather than
your own branch and preserve unrelated work. When
the user asks you to review or integrate a PR or branch, you may inspect, test,
and integrate that contribution regardless
must also add a corresponding subsection to `paper_index.md`.
When reviewing such PRs, ensure that `paper_index.md` was updated.
### Code duplication and consistency
Trainers in this repository are **self-contained by design
behavior, setup, usage, and the docs index
- `CONTRIBUTING.md` for contribution scope, PR format, and review requirements
- `docs/CONTRACTS.md` to find the contract/RFC for the subsystem being changed
- `docs/GUIDELINES.md` for bug-class
apply it to
`megatron/training` or other training-loop code unless the PR explicitly
opts into that migration.
- In reviews, flag new direct `parallel_state.get_*_group()` usage in
`megatron/core` unless
encyclopedia backbone. Promotion is gated by `research_loop.py promote-mechanisms` with a recorded reviewer; ledgers live under `researcher/mechanisms/ledgers/`.
- Claim provenance for numeric or volatile claims lives in `researcher/claims/index.jsonl`. Add an entry