DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to check the harness tests before editing it with Swe Sweep

Run the repo's test suite and lint hooks to get a clean baseline before changes.

Who it is forA developer or coding agent about to modify the SWE-sweep harness or its evaluation code.

The problemChanges to the evaluation code can silently shift scores, so a clean baseline is needed first.

The outcomeA passing test suite and lint run on the unchanged repo, giving a baseline for later edits.

What you need first

  • Python with uv (or pip) installed
  • Harbor, as pinned by the repo
  • A unified diff file (model.patch) made against a task's base commit
  • Docker or the environment Harbor needs for the verifier, if Harbor requires it (inferred)

Steps

  1. git clone https://github.com/facebookresearch/swe-sweep.git
  2. cd swe-sweep
  3. uv sync --extra test
  4. uv run pytest
  5. uvx pre-commit run --all-files

Prompt for your agent

In the facebookresearch/swe-sweep repo, run `uv sync --extra test` then `uv run pytest` and report the pass and fail counts. Confirm that `uvx pre-commit run --all-files` passes before making any edits to <file-to-change>.

Caveat. The README says CI tests on Python 3.12 and 3.13, so a baseline on other Python versions may not match the project's own checks.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page