Skip to content

Weekly repo security and docs pulse

Two weekly runs for people who maintain more repos than they can watch. One opens a single security issue per repo with triaged findings, the other opens one pull request fixing docs that drifted from the code.

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

What it does

  • Runs dependency, secret and workflow scanners and records any scanner that could not run
  • Reads the week's diff for risky changes
  • Groups advisories under the direct dependencies that pull them in
  • Writes changelog lines for users from merged PRs
  • Checks the report for anything that looks like a secret before posting

Your approval boundaries

Creates drafts

These actions always wait for your yes:

  • Merging the docs pull request
  • Fixing anything in the security issue

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 dependency, secret and workflow scanners and records any scanner that could not run. Next, it reads the week's diff for risky changes. Then it groups advisories under the direct dependencies that pull them in. After that, it writes changelog lines for users from merged PRs. Finally, it checks the report for anything that looks like a secret before posting. It works with your git host, package registry 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 merging the docs pull request and fixing anything in the security issue, and says plainly if a step cannot be undone.

“Nothing is merged, deleted or pushed to a default branch. Claude proposes, you decide.”
SouphianeJ SouphianeJ on GitHub · Oct 17, 2026
Before you startGit host · Package registry 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

  • Package registry

    Handles the package registry part of this job. Grant public read access.

    API required: No. Public registries can be read without an account.

    No sign-up needed

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.

e.g. release-please

2Your prompt

4 of 4 still empty
Fill these in before you run it: [REPOS TO WATCH] [RUN DAY] [CHANGELOG TOOL IF ANY: e.g. release-please] [SCANNERS TO RUN] You are the Weekly repo security and docs pulse agent. Two weekly runs for people who maintain more repos than they can watch. One opens a single security issue per repo with triaged findings, the other opens one pull request fixing docs that drifted from the code. 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 dependency, secret and workflow scanners and records any scanner that could not run - Reads the week's diff for risky changes - Groups advisories under the direct dependencies that pull them in - Writes changelog lines for users from merged PRs - Checks the report for anything that looks like a secret before posting What you must never do without a yes from a person: - Merging the docs pull request - Fixing anything in the security issue 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, Claude Desktop with MCP

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. 2Set up Package registry. Keep it to public read access.
  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: merging the docs pull request, fixing anything in the security issue.

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 Weekly repo security and docs pulse](https://trustcase.dev/badge/weekly-repo-security-and-docs-pulse.svg)](https://trustcase.dev/use-cases/weekly-repo-security-and-docs-pulse)
HTML
<a href="https://trustcase.dev/use-cases/weekly-repo-security-and-docs-pulse"><img src="https://trustcase.dev/badge/weekly-repo-security-and-docs-pulse.svg" alt="Trustcase trust score for Weekly repo security and docs pulse" height="20"></a>

More engineering workflows