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

How to run tests, open PRs, and watch CI in an existing repo with QM

Have the agent work inside a repository to run tests, open pull requests, and check CI results.

Credentials. Giving the agent repository access means it can push branches and open pull requests with your permissions, so keep the approval gates on until you trust the workflow.

Who it is forAn engineer on a small team who wants routine repository chores handled while they focus on other work.

The problemRunning tests, opening PRs, and checking CI after each push is repetitive. Engineers context-switch to do it.

The outcomeThe agent runs the test suite in the repository's sandbox, opens a pull request with the change, and reports the CI status.

What you need first

  • Your own cloud account for the deployment, as the README says each deployment runs in the operator's own cloud
  • Your own model keys and provider choice, since the README says deployments use your own models and keys
  • Node.js and npm to run the qm CLI and npm install (inferred from the npm commands in the README)
  • A Postgres database for durable sessions, set through DATABASE_URL
  • Optional: a Slack workspace where you can grant access, if you want Slack rather than web only

Steps

  1. Deploy a QM instance and sign in to the web app.
  2. Connect the target repository to the scope's sandbox and grant the agent access to it, since the README says each scope has its own isolated sandbox but does not list the exact connection steps. (inferred, check the README)
  3. Ask the agent in the web app or Slack to run the test suite and report failures.
  4. Ask the agent to open a pull request with the change and monitor the CI run until it finishes.

Prompt for your agent

Using the repository yc-software/qm, deploy a QM instance and connect the repository <repository URL> to its sandbox. Have the agent run the tests, open a pull request for <branch name>, and report the CI result. Verify that the pull request exists and that the CI run has a status before reporting success.

Caveat. The README lists this as a supported workflow but does not describe how repository access is granted, so verify the sandbox setup in the deployment docs before relying on it.

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