Initial SearchAgent-Zero import

Author: NLPJCL

.agent/skills/issue.md

@@ -0,0 +1,47 @@
+---
+name: issue
+description: Create or update a GitHub issue following verl project conventions.
+user_invocable: true
+---
+
+When the user asks to create or update an issue, follow these steps:
+
+### 1. Gather Context
+
+Read the following to understand available issue types and their required fields:
+
+- [`bug-report.yml`](.github/ISSUE_TEMPLATE/bug-report.yml)
+- [`feature-request.yml`](.github/ISSUE_TEMPLATE/feature-request.yml)
+
+If updating an existing issue, read its current title, body, labels, and comments first.
+
+### 2. Determine Issue Type
+
+Based on the user's description, select the appropriate template:
+
+- **Bug report** ([`bug-report.yml`](.github/ISSUE_TEMPLATE/bug-report.yml)) — something is broken or behaves unexpectedly
+- **Feature request** ([`feature-request.yml`](.github/ISSUE_TEMPLATE/feature-request.yml)) — a new capability or enhancement
+- **Blank issue** — if neither template fits
+
+### 3. Compose the Issue
+
+Fill in the template fields based on information from the user and the codebase. For bug reports, run `python scripts/diagnose.py` to gather system info if possible.
+
+When updating, ensure the title and body still accurately reflect the current state of the issue.
+
+### 4. Check for Duplicates
+
+Search for existing issues before creating:
+
+```
+gh issue list --repo verl-project/verl --state open --search "<keywords>"
+```
+
+If a duplicate exists, inform the user instead of creating a new one.
+
+### 5. Create or Update the Issue
+
+- **Create**: add `good first issue` and/or `call for contribution` labels if the issue is straightforward and suitable for new contributors.
+- **Update**: update title, body, and labels as needed.
+
+Return the issue URL when done.

.agent/skills/pr.md

@@ -0,0 +1,33 @@
+---
+name: pr
+description: Create or update a pull request following verl project conventions.
+user_invocable: true
+---
+
+When the user asks to create or update a PR, follow these steps:
+
+### 1. Gather Context
+
+Read the following and understand the current branch's changes compared to main:
+
+- [`CONTRIBUTING.md`](CONTRIBUTING.md)
+- [`PULL_REQUEST_TEMPLATE.md`](.github/PULL_REQUEST_TEMPLATE.md)
+
+If a PR already exists for this branch, also read its current title, body, and review comments.
+
+### 2. Compose PR Title and Body
+
+Follow the PR template strictly for both title format and body sections. Only check checklist boxes for steps that have actually been completed.
+
+When updating, ensure the title and body still accurately reflect **all** changes on the branch, not just the latest commit.
+
+### 3. Pre-submit Checks
+
+Run pre-commit and fix any issues before creating or pushing.
+
+### 4. Create or Update the PR
+
+- **Create**: target `main` by default unless the user specifies otherwise.
+- **Update**: push new commits and update the title and body if the scope has changed. **Read the current PR title and body first** and incorporate any edits the user may have made directly on GitHub — never overwrite with a version generated from scratch.
+
+Return the PR URL when done.

.claude/skills/issue.md

@@ -0,0 +1 @@
+../../.agent/skills/issue.md

.claude/skills/pr.md

@@ -0,0 +1 @@
+../../.agent/skills/pr.md

.codex/skills/issue.md

@@ -0,0 +1 @@
+../../.agent/skills/issue.md

.codex/skills/pr.md

@@ -0,0 +1 @@
+../../.agent/skills/pr.md

.gemini/config.yaml

@@ -0,0 +1,10 @@
+have_fun: false
+code_review:
+  disable: false
+  comment_severity_threshold: HIGH
+  max_review_comments: -1
+  pull_request_opened:
+    help: false
+    summary: false
+    code_review: true
+ignore_patterns: []

.git-blame-ignore-revs

@@ -0,0 +1,13 @@
+# Local uasge: git config blame.ignoreRevsFile .git-blame-ignore-revs
+
+# [dev] feat: immigrate from yapf & pylint to ruff based on pre-commit
+# Changed 268 files, +10k/-9k lines. This is the biggest formatter change.
+b00f77d8559b48d57a33c0132a5ba1c81891a536
+
+# [ci] refactor: reduce ruff line-length from 300 to 120
+# Changed 238 files, +6k/-1k lines. Global formatting change.
+00a10a8ef389556f957a2f36132b2358fd6a109f
+
+# [Lint] fix: linting errors in all files
+# Changed 179 files, +1k/-3k lines. Global lint fix.
+8e5ad4688a13de81727c014a3c2e2fb26324bc20

.github/CODEOWNERS

@@ -0,0 +1,25 @@
+/docs @eric-haibin-lin @zhaochenyang20 @hongpeng-guo
+/docs/amd_tutorial @yushengsu-thu
+/docs/slang_multiturn @zhaochenyang20 @SwordFaith
+/docs/ascend_tutorial @wucong25
+
+/third_party/sglang @zhaochenyang20 @SwordFaith
+/third_party/vllm @PeterSH6 @wuxibin89
+
+/examples/grpo_trainer @vermouth1992 @PeterSH6 @tardis-key @wucong25 @ji-huazhong
+
+/verl/single_controller @zw0610 @wuxibin89 @hongpeng-guo
+/verl/trainer @eric-haibin-lin @vermouth1992 @tongyx361 @PeterSH6
+/verl/models/mcore @ISEEKYAN @vermouth1992
+/verl/models/transformers @vermouth1992 @PeterSH6 @tardis-key @wucong25 @ji-huazhong
+/verl/workers/engine @eric-haibin-lin @vermouth1992 @ZihengJiang
+/verl/workers/roles @eric-haibin-lin @vermouth1992 @ZihengJiang
+/verl/workers/engine/fsdp @eric-haibin-lin @vermouth1992 @ZihengJiang
+/verl/workers/rollout/vllm_rollout @wuxibin89 @PeterSH6 @chenhaiq
+/verl/workers/rollout/sglang_rollout @zhaochenyang20 @SwordFaith @chenhaiq
+/verl/workers/engine/megatron @ISEEKYAN @vermouth1992
+/verl/experimental @wuxibin89 @ArronHZG
+
+/tests/single_controller @zw0610 @wuxibin89
+/tests/trainer @eric-haibin-lin @vermouth1992 @tongyx361 @PeterSH6
+/tests/workers/rollout/vllm_rollout @wuxibin89 @PeterSH6 @chenhaiq

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,65 @@
+# modified from https://github.com/huggingface/transformers/blob/main/.github/ISSUE_TEMPLATE/bug-report.yml?plain=1
+name: "\U0001F41B Bug Report"
+description: Submit a bug report to help us improve verl
+labels: [ "bug" ]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report! 🤗
+
+  - type: textarea
+    id: system-info
+    attributes:
+      label: System Info
+      description: Please share your system info with us. You can run the command `python scripts/diagnose.py` and copy-paste its output below.
+      placeholder: verl version, platform, python version, ...
+    validations:
+      required: true
+
+  - type: checkboxes
+    id: information-scripts-examples
+    attributes:
+      label: Information
+      description: 'The problem arises when using:'
+      options:
+        - label: "The official example scripts"
+        - label: "My own modified scripts"
+
+  - type: checkboxes
+    id: information-tasks
+    attributes:
+      label: Tasks
+      description: "The tasks I am working on are:"
+      options:
+        - label: "An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)"
+        - label: "My own task or dataset (give details below)"
+
+  - type: textarea
+    id: reproduction
+    validations:
+      required: true
+    attributes:
+      label: Reproduction
+      description: |
+        Please provide a code sample that reproduces the problem you ran into. It can be a Colab link or just a code snippet.
+        Please include relevant config information with your code.
+        If you have code snippets, error messages, stack traces please provide them here as well.
+        Important! Use code tags to correctly format your code. See https://help.github.com/en/github/writing-on-github/creating-and-highlighting-code-blocks#syntax-highlighting
+        Do not use screenshots, as they are hard to read and (more importantly) don't allow others to copy-and-paste your code.
+
+      placeholder: |
+        Steps to reproduce the behavior:
+
+          1.
+          2.
+          3.
+
+
+  - type: textarea
+    id: expected-behavior
+    validations:
+      required: true
+    attributes:
+      label: Expected behavior
+      description: "A clear and concise description of what you would expect to happen."