Skip to content

Morning QA report

Runs a set of read-only checks on your codebase each morning and files one report issue. It starts as an observer and only gets more power when you grant it.

EngineeringWorks with Claude Code · Cursor+1Community example
Build your promptSee requirements

What it does

  • Runs the checks you list on a schedule
  • Compares results with the last run
  • Writes what broke or drifted in plain words
  • Files one report issue for the day

Your approval boundaries

Creates drafts

These actions always wait for your yes:

  • Editing any code
  • Opening pull requests
  • Closing or changing other issues

You decide what happens next.

More about this workflow

This setup is for developers and small engineering teams who want fewer chores. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it runs the checks you list on a schedule. Next, it compares results with the last run. Then it writes what broke or drifted in plain words. Finally, it files one report issue for the day. It works with your git host, CI and monitoring, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before editing any code, opening pull requests and closing or changing other issues, and says plainly if a step cannot be undone.

“runs read-only morning checks and posts one report issue a day”
PecanStreetAI PecanStreetAI on GitHub · Aug 27, 2026
Before you startGit host · CI accessScoped permissionsClaude Code or Cursor
Explore required tools and model recommendations

Tools and access

  • GitHub

    Handles the git host and ci part of this job. Grant a fine-grained token, read code and write comments.

    API required: Yes. Needs a GitHub App or a fine-grained personal access token scoped to the repos it needs.

    Sign up: Create a GitHub account

  • Sentry

    Handles the monitoring part of this job. Grant read-only token.

    API required: Yes. Needs an auth token from your Sentry account.

    Sign up: Sentry

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Claude Opus 5.5

Its maker points to it for long running coding work.

$4 per million input tokens, $20 per million output tokens.

Anthropic docs as of October 11, 2026

Cheaper backup

Claude Sonnet 5.5

Half the price per token and still strong for reviews and docs.

$2 per million input tokens, $10 per million output tokens.

Anthropic docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

tests, build, key pages

e.g. 6 AM weekdays

2Your prompt

4 of 4 still empty
Fill these in before you run it: [YOUR REPO] [CHECKS TO RUN: tests, build, key pages] [WHEN TO RUN: e.g. 6 AM weekdays] [WHO READS THE REPORT] You are the Morning QA report agent. Runs a set of read-only checks on your codebase each morning and files one report issue. It starts as an observer and only gets more power when you grant it. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Runs the checks you list on a schedule - Compares results with the last run - Writes what broke or drifted in plain words - Files one report issue for the day What you must never do without a yes from a person: - Editing any code - Opening pull requests - Closing or changing other issues Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, Cursor, OpenAI Agents SDK

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect GitHub with its own login, not yours. Grant a fine-grained token, read code and write comments.
  2. 2Connect Sentry with its own login, not yours. Grant read-only token.
  3. 3Paste the prompt where your harness takes instructions. See the note under the Copy button.
  4. 4Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  5. 5Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access24 / 30

Writes drafts and notes inside your tools, nothing leaves on its own.

Human approval30 / 30

Waits for a yes on: editing any code, opening pull requests, closing or changing other issues.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 84.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Morning QA report](https://trustcase.dev/badge/morning-qa-report.svg)](https://trustcase.dev/use-cases/morning-qa-report)
HTML
<a href="https://trustcase.dev/use-cases/morning-qa-report"><img src="https://trustcase.dev/badge/morning-qa-report.svg" alt="Trustcase trust score for Morning QA report" height="20"></a>

More engineering workflows

  • Upstream blocker recheck

    Once a month, re-tests the upstream bugs and missing releases your work is waiting on. Tells you which ones have cleared.

  • Daily public exploit digest

    Each day it checks public exploit sources for high severity flaws that just got working exploit code. It keeps one running monthly list so you know what to patch first.

  • Safe dependency update pull requests

    Finds outdated packages on a schedule, applies only small updates that pass your tests, and opens a pull request. Major updates are listed for a person.

  • Overnight safe task picker

    Each night it looks over the day's unfinished work and picks 3 to 5 coding tasks that are safe to run overnight. It only writes a report with a ready prompt for each one.