# A weekly work report your client reads, built from your pull requests · Stacktree Source: https://stacktr.ee/weekly-work-report [Skip to content](#main) PFrom Product Hunt? Your first pages are free, no card. Code `PRODUCTHUNT` takes 50% off your first month of Studio.[Start free →](https://app.stacktr.ee/?join=1&from=producthunt) × A Stacktree customer sent you. Your first month is 50% off on any plan, taken off at checkout. [Start free →](https://app.stacktr.ee/?join=1&from=referral) × [stacktr.ee](/) [Examples](/#proof) [How it works](/#how) [Pricing](/pricing) [Security](/security) [Log in](https://app.stacktr.ee) [Publish one](https://app.stacktr.ee/?join=1) By [Steve Smith](/about) · Founder, Stacktree Last updated November 2, 2026 Weekly work report # Every Friday, the week’s pull requests become a report your client reads. Your agent reads what merged and what is waiting for review, writes it up for someone who doesn’t read code, and publishes it as a page filed under the client. Every week collects at one address, newest first. [Publish a report free →](https://app.stacktr.ee/?join=1&from=seo_weekly_work_report) [Copy the prompt](#set-it-up) No GitHub account for your client Only the report is published See who opened it The week's pull requests from four repositories arrive one at a time. Each one becomes a plain-language line in a report called Work Delivered, under Shipped or Open for review. The figures count up to 4 merged, 5 open for review, 4 repos and 11 review findings. The report is filed under Acme Travel as week 44, and Dana opens it on Saturday at 09:12. Then the next week's report is written the same way.This week on GitHubgh pr list · 4 repos- emails #14mergedfeat: quote follow-ups+0−0in report → - site #212mergedfix(forms): honeypot+0−0in report → - crm #41mergedchore: dedupe pass 1+0−0in report → - app #96openfeat: offline trip docs+0−0in report → - site #215openfeat: 301s for old URLs+0−0in report → - site #208mergedfix: tour dates in UTC+64−22in report → - emails #12mergedfeat: quote template v2+318−140in report → - crm #38mergedfeat: import bookings+512−9in report → - app #94openfeat: trip map+870−31in report → - site #210openfeat: new tour pages+1,120−12in report → + 2 more pull requestsPublished for Acme Travelacme.northbank.studio/week-43Northbank Studio · 19 to 23 October 2026Work DeliveredShipped, open for review, and the analysis behind it.3merged4open for review4repos7review findingsShippedStarted and merged this week.- Tour dates in the visitor’s own time20 Octsite #208They were an hour off for UK visitors. - A clearer quote email21 Octemails #12Price, dates and what is included, in that order. - Bookings land in the CRM by themselves22 Octcrm #38No more copying them in by hand. Open for reviewWritten, verified, waiting on a merge.- A map for each day of the trip23 Octapp #94needs a callA pin for every stop. - Four new tour pages23 Octsite #210for DanaCopy to check before they go live. Filed under Acme Travel · Week 43DOpened by Dana · Mon 08:40 Live Northbank Studio’s week 44 report for Acme Travel. An example, retold from a real client report. How it runs ## Your agent reads the code. Your client reads the page. Three steps, the same every Friday, so every report has the same shape and the client knows where to look for what needs them. 01 ### Your agent reads the week’s pull requests. In Claude Code it uses the gh CLI with your own GitHub login, across every repo you name: `gh pr list -s merged`what shipped since Monday `gh pr list -s open`what is waiting for review `gh pr view --comments`the review findings and why `gh pr diff`what actually changed 02 ### It writes them up for someone who doesn’t read code. What shipped and what it changes for the business. What is open for review, what it is waiting on, and the decision the client needs to make. The analysis behind the work. Plain sentences, with the repo and pull request number beside each one for anyone who wants them. 03 ### It publishes the report under the client. Filed under the client, this week’s report lands on top of last week’s at the client’s own address, newest first. Send the link on Friday, or let them bookmark the address once. Why a page ## A list of pull requests tells your client what you typed. The report tells them what changed. ### A PR list - ×fix(forms): honeypot + submit-time checkAccurate, and it means nothing to the person paying for it. - ×Decisions buried in review threadsThe question that blocks a merge sits in a comment the client will never see. - ×A recap email nobody can findLast month’s update is somewhere in an inbox, under a subject line nobody remembers. ### The report your client reads - ✓Bots and blank forms blocked on both quote formsThe same pull request, in their words: junk inquiries went from about 30 a day to 2. - ✓What is waiting on them, said plainlyOpen for review, with the call to make and whose call it is. - ✓Every week at the same addressLast week’s report is one tap away, and next week’s lands on top of it. Every week at one address ## Week 44 on top, every week before it underneath. File each report under the client and it joins everything else you have sent them, at their own address, newest first. They bookmark it once. On paid plans you see who opened each one, by name. Filing work by client is free on every plan. The client’s own address starts on Solo. acme.northbank.studio Northbank StudioPrivate Acme Travel Everything delivered for this engagement, in one place. 14documents Aug 2026working together since 30 Octlast updated October 2026 4 documents - 30 Oct Newest · Week 44 Work delivered · 26 to 30 Oct 4 merged, 5 open for review, 11 review findings Open → - 23 OctWork delivered · 19 to 23 OctWeek 43 - 16 OctWork delivered · 12 to 16 OctWeek 42 - 09 OctWork delivered · 5 to 9 OctWeek 41 DM Opened by Dana and MarcusWeek 44 · first opened Sat 09:12 Set it up ## One prompt, then a schedule. Paste this into Claude Code with Stacktree connected. Fill in the client, the repos and Monday’s date, and read the first report before you send it. Prompt for Claude CodeCopy ``` Write this week's work report for . 1. With the gh CLI, list the pull requests in : the ones merged since Monday (gh pr list --state merged --search "merged:>=") and the ones still open. Read each one's description, review comments and diff. 2. Write the report as one HTML page for someone who doesn't read code, titled "Work delivered · ". Open with four figures: merged, open for review, repos and review findings raised. Then three sections. Shipped: one plain sentence per pull request on what changed for the business, with the repo and number beside it. Open for review: what each one does, what it is waiting on, and any decision the client needs to make. Analysis and review: the investigation that steered the code. 3. Publish it to Stacktree under the client "" with comments on, and send me the link. ``` The schedule is your agent’s, not ours: save the prompt as a Claude Code routine for Friday afternoons, or run it from a cron job. Each run publishes a new report under the same client, so the address keeps every week. S Our agent turned a week of pull requests across four repos into one page written for the client: what shipped, what was waiting for review, and why it mattered. Steve Smith, who built Stacktree. [How we use Stacktree →](/how-we-use-stacktree) FAQ ## What people ask before they send one Does my client need a GitHub account? + No. They get a link to a page and open it in any browser, phone included. They never see the repos, and there is nothing to sign up for. What about private repos? + Your agent reads them where it already has access: on your machine, with your own GitHub login. Stacktree never connects to GitHub. Only the report the agent writes is published, so say in the prompt what it may and may not quote. Can I keep the report private? + Yes. Links are unguessable by default, you can add a passcode on any plan, and paid plans add your own domain, a company-email gate and one address per client where every report you send them collects. What if a week is quiet? + Then the report is short and says so. Two fixes merged and nothing waiting on the client is still worth a page: they know work happened and that nothing is blocked on them. If you would rather skip a week with nothing merged, put that in the prompt. Can the client comment on it? + Yes. They select any line and leave a comment, from any browser or phone, with no login. Your agent reads new comments with list_feedback and answers each one with resolve_feedback; the client sees the reply the next time they open the page, on any device when you sent them their own named link, and by email when the report asks for their email. How do I know they read it? + On paid plans you see who opened each report, by name, and when. Give Dana and Marcus each their own link and every open comes back with their name. Your agent can ask Stacktree for the same list. [Client project tracker](/client-project-tracker) [Tester kit](/tester-kit) [Client spaces](/client-spaces) [Recurring client report](/workflows/recurring-client-report) [Send a client report as a link](/send-client-report-as-link) ## Send this Friday’s report as a page. Your client never needs an account. Free to start: a free page lasts 7 days, and up to 90 while your client keeps opening it. Paid plans keep it for as long as the work runs. [Publish a report free →](https://app.stacktr.ee/?join=1&from=seo_weekly_work_report) stacktr.ee [Page video](/page-video) [Ask this page](/ask-this-page) [Client feedback](/client-feedback-loop) [Client spaces](/client-spaces) [Templates](/templates) [Use cases](/use-cases) [Integrations](/agents) [Alternatives](/alternatives) [About](/about) [Blog](/blog) [Changelog](/changelog) [Pricing](/pricing) [Security](/security) [FAQ](/faq) [Made with Stacktree](/made-with) Building with AI agents? See the [developer docs →](/developers) [Send your first link free](https://app.stacktr.ee/?join=1&from=sticky_weekly_work_report) No card · 3 pages free --- Full markdown summary of the Stacktree marketing surface: https://stacktr.ee/llms-full.txt