Agents In Use
What’s new todayLast update
3 use cases added today

Run exploratory pre-production QA with Claude

u/Sad_Republic_7705 integrated Claude into CI after a successful pre-production deployment. It uses commit differences, Linear tickets and PR descriptions to explore changed flows. The author reports catching bugs they missed.

OUR ADAPTATION

Suggested prompt

Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.

Review this exact pre-production build using its commit diff, linked issue descriptions and PR context. Exercise the changed happy paths and nearby failure cases. For each suspected bug, report the build identifier, starting state, reproduction steps, expected result and actual result. Do not approve or deploy a release.

Evidence at a glance

Sourced account
Source poster / publisher
u/Sad_Republic_7705
Original account
Read the source ↗
Published
Source link checked
Reported result
The author reports that the CI-based QA workflow has already found bugs they did not catch themselves. The source does not provide a bug count, reproduction evidence or a measured detection rate.
Human involvement
The author maintains the workflow and assesses its findings. They are asking how to scale it; the proposed rate of 10 to 20 PRs daily is a future goal, not demonstrated throughput.

A linked account supports attribution. It does not mean we independently reproduced its result.

Report an issue with this caseOpen correction email

Opens your email app with the case link included. Nothing is sent automatically.

How the agent did it

  1. After a merge and successful deployment to pre-production, CI starts the Claude QA task.
  2. Claude uses the changes between pre-production and production, relevant Linear tickets and PR descriptions as context.
  3. It attempts the expected user journey and explores nearby failure cases, with the author reviewing the results.

Reddit user u/Sad_Republic_7705 describes adding Claude as a QA tester to a deployment pipeline. The task runs after a successful deployment to pre-production. In a follow-up comment, the author clarifies that the PR is already merged and closed at that point. This is post-deployment testing in a staging environment, not a review that blocks the initial merge.

Claude receives context from the differences between pre-production and production, related Linear tickets and PR descriptions. It attempts the expected user journey, then pushes into nearby cases that might reveal bugs. The author says this has already caught problems they had not found themselves. No examples or independently reproduced failures are supplied.

The source also makes the limits clear. The author is still working out how to scale the process and asks for advice. Their ambition to handle 10 to 20 PRs a day is not an observed result. The post does not demonstrate a detection rate, reliable release approval or production promotion by the agent.

The useful pattern is giving exploratory QA both code-change context and the intended behaviour described in tickets. Anyone adapting it would need to tie each result to a specific build and review reported failures before relying on them. Those are suggested safeguards, not additional capabilities demonstrated by this account.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: Reddit · u/Sad_Republic_7705

Frequently asked questions

When does the Claude QA task run?

The author clarifies that it runs in CI after a merge and successful deployment to pre-production, when the PR is already closed.

What result does the author report?

They say the workflow has caught bugs they missed themselves. The source does not supply a bug count or independently reproducible examples.

More details

About this account

CI initiates Claude's exploratory QA after deployment to pre-production. The source does not establish that the agent can promote a build to production or approve a release.

Firsthand account by u/Sad_Republic_7705: https://www.reddit.com/r/ClaudeCode/comments/1xakqs9/monkey_proofing_my_release_with_sonnette_55/. Public RSS post and returned comments captured on 22 October 2026; RSS coverage is partial. Body eligibility passed at 0.84. Results are author-reported, not independently reproduced. Suggested prompt by Agents In Use, not the author's original prompt.

Credit: u/Sad_Republic_7705 on Reddit

Source published

Added to Agents In Use

Source checked

Tools and topics

Claude · CI pipeline · Linear

QA · CI · pre-production

Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.