.agents

Imported from VectorSpaceLab/Search-SWE (.agents/AGENTS.md). Install upstream with npx skills add VectorSpaceLab/Search-SWE --skill .agents. Copyright stays with the author.

Search-SWE Task Workflow

This is the contributor workflow entry point. Detailed task-authoring knowledge lives inside the skill, not here. Paths below are relative to the repository root unless expressed as Markdown links.

Route the request

• Create or substantially revise a task: load create-searchswe-task and follow its workflow, references, and validation gates. If no native skill loader is available, open that SKILL.md directly. It can also be invoked independently as $create-searchswe-task; it does not need this file.
• Review, promote or finalize a task PR as maintainer: load maintain-searchswe-task, independently invocable as $maintain-searchswe-task. Default to read-only gh evidence review; use its bundled offline promotion/HF staging helpers only at approved stages.
• Run an existing task: use docs/quickstart.md; do not scaffold a task.
• Restore fixed inputs: use docs/assets.md and the existing download tools.
• Edit project documentation: keep README.md and README_zh.md aligned. The current public modes are Implementation and Optimization.
• Change shared images: use docker/README.md. An ordinary task contribution should reuse the CPU/GPU images rather than redesign their shared runtime.

Coordinate the work

1. Inspect the worktree and agree on the requested deliverable. Preserve other contributors' changes. Ask about uncertainties that affect task design or authorization, not information already supplied by the user.
2. For task contributions, let the skill drive design → authoring → validation. Before scaffolding, inspect one or two closest reviewed packages under tasks/ as read-only structural precedents, selected by mode, grading shape, resources and hardware. Current repository contracts and validators override older examples; never inherit task-specific data, thresholds, licenses or access merely because another task uses them. A PR may add multiple tasks, all under exactly one first-name namespace, at task-submissions/<first-name-slug>/<1|2>-x-<positive-ordinal>; do not use usernames, reuse a promoted temporary ordinal, or guess formal IDs. Follow CONTRIBUTING.md and docs/contributing.md: require actual authors and explicit --task-path for local trials, then promote every task with its own same-PR pure rename and finalization commits before a merge commit (no squash/rebase). Track which stage is complete and which inputs or approvals are missing. Do not duplicate the skill's specifications in this file.
3. Keep changes within the selected task plus directly necessary integration changes. Updating a website, publishing a dataset, pushing images, and opening or merging a PR are separate actions, not implied by task creation.
4. Review the resulting diff and validation evidence. Hand off changed paths, task mode/hardware, commands actually run, observed results, and blockers. Static checks alone are not evidence of a working end-to-end benchmark.

Agents are not guaranteed to auto-load an AGENTS.md located under .agents/ when editing tasks/. Open this entry point explicitly or invoke the skill; do not assume its directory placement grants repository-wide instruction scope.