Skip to content

Stale dependency pull request watch

On a schedule it looks at the open Dependabot pull requests across your organization, sorts them by severity and flags any past the review deadline you set. For stale ones it drafts a short analysis to post as a comment so a reviewer can decide faster.

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

What it does

  • Lists open Dependabot pull requests across the enrolled repos
  • Classifies each by severity and age against your SLA
  • Flags breaches in a weekly org report alongside merged PRs and CI health
  • Writes a short analysis for stale updates: what changed, the risk, and what blocks review

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Posting the analysis comment on a pull request
  • Merging anything

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 lists open Dependabot pull requests across the enrolled repos. Next, it classifies each by severity and age against your SLA. Then it flags breaches in a weekly org report alongside merged PRs and CI health. Finally, it writes a short analysis for stale updates: what changed, the risk, and what blocks review. It works with your git host and CI, 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 posting the analysis comment on a pull request and merging anything, and says plainly if a step cannot be undone.

“Monitor Dependabot PRs, classify by severity, flag SLA breaches”
rossoctl rossoctl on GitHub · Oct 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

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.

by severity

2Your prompt

4 of 4 still empty
Fill these in before you run it: [ORG OR REPO LIST] [SLA DAYS: by severity] [REPORT DAY] [WHERE TO SEND THE REPORT] You are the Stale dependency pull request watch agent. On a schedule it looks at the open Dependabot pull requests across your organization, sorts them by severity and flags any past the review deadline you set. For stale ones it drafts a short analysis to post as a comment so a reviewer can decide faster. 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: - Lists open Dependabot pull requests across the enrolled repos - Classifies each by severity and age against your SLA - Flags breaches in a weekly org report alongside merged PRs and CI health - Writes a short analysis for stale updates: what changed, the risk, and what blocks review What you must never do without a yes from a person: - Posting the analysis comment on a pull request - Merging anything 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. 2Paste the prompt where your harness takes instructions. See the note under the Copy button.
  3. 3Do 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.
  4. 4Read 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.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: posting the analysis comment on a pull request, merging anything.

Undo and logs14 / 20

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

Scope18 / 20

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

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • 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: Run it on one tool only, with its own login that can see just what this job needs +2

Do all of these to reach 91, up from 80.

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 Stale dependency pull request watch](https://trustcase.dev/badge/stale-dependency-pull-request-watch.svg)](https://trustcase.dev/use-cases/stale-dependency-pull-request-watch)
HTML
<a href="https://trustcase.dev/use-cases/stale-dependency-pull-request-watch"><img src="https://trustcase.dev/badge/stale-dependency-pull-request-watch.svg" alt="Trustcase trust score for Stale dependency pull request watch" height="20"></a>

More engineering workflows

Other workflows that use the same tools

  • Site change tester

    Marketing. Tries small edits to your site, watches whether more visitors stay, and keeps only the changes that help. Good for steady small wins on a landing page.

  • Daily kids lesson builder

    Personal. Builds a short interactive lesson for your kids each night and has a second agent check it. You read a review email and approve it before the kids get the link.

  • Weekly delivery status report

    Operations. Pulls your team's work items once a week and builds a status report grouped by initiative. It puts at risk items first and flags anything with no update in two weeks.