formatting, lint, and test commands for
the code you changed.
- Before handing back substantive code changes, run `composer check` when
feasible and call out anything you could
files. Review instructions prohibit repairs
and warn that other nodes may execute concurrently; this is an instructional boundary. Missing
dependencies are reported with environment evidence rather than unrelated code repair
layer.
- `extension-toolkit/vscode` may depend on `base` and the VS Code API.
- Production code must not import `extension-toolkit/vscode/testing`.
- Import an explicit toolkit layer; do not import from
human-written summaries save the maintainer from having to parse
lengthy generated text.
- Review all code in your PR yourself and vouch for its quality.
## Contributing
This is an Emacs
chart that retains an immutable
`nvcr.io/nvstaging/vss-core/*` default, ignores either global override, or
hard-codes a managed image in an umbrella profile as drift.
- Continue to flag every other semantic
links there, and (e) flag that this is an
**auto-generated adapter for the reviewer to check**. The fork
comment (`adapter-note-…md`) instead says the bot can't push
never displaces `latest`. Both release workflows share the `npm-publish` concurrency group.
### Bonk (AI codereview)
Mention `/bonk` or `@ask-bonk` in PR comments to get AI-powered codereview
brand file
there, never copy one into `examples/`, and **do not move code between
`hosted/` and `waku/` without saying which license it lands under.**
8. **Don't edit the copied
Verify compatibility**: Ensure changes don't break backward compatibility without explicit approval
### For CodeReviews
When assisting with codereviews:
1. Check compliance with [Azure Go SDK Guidelines](https://azure.github.io
configuration, or recommended usage changes.
## Go design conventions
Follow Effective Go and the Go CodeReview Comments, while preserving
established APIs when compatibility requires it.
- Use `gofmt` and `goimports
verification
succeeds against the public release.
---
## Compiler and Test Checks (CRITICAL)
**After any substantive code changes, use the one authoritative quality entry
point:**
```bash
dsr quality --tool pi_agent_rust
open
`SKILL.md` format, cross-provider). Shared skills, convention rules, `/create-pr`,
`/create-changeset`, `/create-branch`, `/create-issue`, the `code-reviewer` subagent, and the
`house` output style come from the `agents` plugin
([stijnvanhulle/agents](https://github.com
have to review; only per-community skills, which
describe that specific codebase, are written into the repo.
| Host | Skills | Slash commands | Sub-agents | Enforcement hooks |
| --- | --- | --- | --- | --- |
| Claude Code | `~/.claude/skills/` | `~/.claude/commands/` | `~/.claude/agents