Skip to content

Weekly manager report from your commits

Reads a week of your commits across your repos and writes a status report in the exact format your manager asked for. It asks about work git cannot show before you send it.

EngineeringWorks with Claude Code · CursorCommunity example
Build your promptSee requirements

What it does

  • Pulls your commits from the past week across every repo in scope
  • Checks last week's next week items and asks why any carried over
  • Groups commits into one bullet per shipped outcome
  • Marks unmerged work as built, not shipped
  • Asks about setup work and documents that left no commit

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Sending the report to your manager
  • Including any item you have not confirmed

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 pulls your commits from the past week across every repo in scope. Next, it checks last week's next week items and asks why any carried over. Then it groups commits into one bullet per shipped outcome. After that, it marks unmerged work as built, not shipped. Finally, it asks about setup work and documents that left no commit. It works with your git host and notes app, 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 sending the report to your manager and including any item you have not confirmed, and says plainly if a step cannot be undone.

“The skill always asks before finalizing, rather than silently omitting them.”
zayan-work zayan-work on GitHub · Sep 19, 2026
Before you startGit host · Notes app accessScoped permissionsClaude Code or Cursor
Explore required tools and model recommendations

Tools and access

  • GitHub

    Handles the git host 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

  • Notion

    Handles the notes app part of this job. Grant only the pages it needs, read first.

    API required: Yes. Needs a Notion integration. You choose which pages it can see by sharing them with it.

    Sign up: Notion

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.

quoted as they wrote them

2Your prompt

4 of 4 still empty
Fill these in before you run it: [YOUR GIT AUTHOR NAME] [REPOS TO SCAN] [MANAGER'S FORMAT RULES: quoted as they wrote them] [DUE DAY] You are the Weekly manager report from your commits agent. Reads a week of your commits across your repos and writes a status report in the exact format your manager asked for. It asks about work git cannot show before you send 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: - Pulls your commits from the past week across every repo in scope - Checks last week's next week items and asks why any carried over - Groups commits into one bullet per shipped outcome - Marks unmerged work as built, not shipped - Asks about setup work and documents that left no commit What you must never do without a yes from a person: - Sending the report to your manager - Including any item you have not confirmed 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

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 Notion with its own login, not yours. Grant only the pages it needs, read first.
  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.

Access18 / 30

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

Human approval30 / 30

Waits for a yes on: sending the report to your manager, including any item you have not confirmed.

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 Weekly manager report from your commits](https://trustcase.dev/badge/weekly-manager-report-from-your-commits.svg)](https://trustcase.dev/use-cases/weekly-manager-report-from-your-commits)
HTML
<a href="https://trustcase.dev/use-cases/weekly-manager-report-from-your-commits"><img src="https://trustcase.dev/badge/weekly-manager-report-from-your-commits.svg" alt="Trustcase trust score for Weekly manager report from your commits" height="20"></a>

More engineering workflows

Other workflows that use the same tools

  • Evidence first support replies

    Support. Works the support queue a couple of times a day, checking bug reports against the code before drafting a reply. The owner reviews every reply before it goes out.

  • Printed morning newspaper from your notes

    Personal. Every night a routine picks the next unprinted note from a folder and writes it up as a two page newspaper issue. A build step lays it out and checks every page, and a small board on your Wi-Fi prints it at the time you chose.

  • Friday business review from the week's history and notes

    Operations. On Fridays it reads the week's commit history, your notes and last week's review before asking anything. Then it writes what shipped, what is stuck with a next move and an owner, the decisions made and the one thing to automate next.