Skip to content

Client site request handler

Turns a client's text message about their website into a proposed code change ready for review. Made for a freelancer who maintains a small site for a client.

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

What it does

  • Reads the client request
  • Finds the page or file to change
  • Makes the edit on a branch
  • Sends a preview link for review

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Publishing changes to the live site
  • Replying to the client

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 reads the client request. Next, it finds the page or file to change. Then it makes the edit on a branch. Finally, it sends a preview link for review. It works with your git host and chat, 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 publishing changes to the live site and replying to the client, and says plainly if a step cannot be undone.

david he @beetz12 · Sep 26, 2026
Before you startGit host · Chat 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

  • Slack

    Handles the chat part of this job. Grant a bot token in the channels it needs.

    API required: Yes. Needs a Slack app created in your workspace. It gets a bot token with the scopes you approve.

    Sign up: Create a Slack app

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.

2Your prompt

3 of 3 still empty
Fill these in before you run it: [YOUR REPOS] [THE CLIENT AND HOW REQUESTS ARRIVE] [WHO REVIEWS CHANGES] You are the Client site request handler agent. Turns a client's text message about their website into a proposed code change ready for review. Made for a freelancer who maintains a small site for a client. 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: - Reads the client request - Finds the page or file to change - Makes the edit on a branch - Sends a preview link for review What you must never do without a yes from a person: - Publishing changes to the live site - Replying to the client 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, LangGraph

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 Slack with its own login, not yours. Grant a bot token in the channels it needs.
  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: publishing changes to the live site, replying to the client.

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

More engineering workflows

  • Trending repo scout

    Finds the top trending open source repos each day and sums them up so you can spot tools worth using. Useful if most of your stack is built on open source.

  • Integration research sweep

    Checks a long list of products for APIs, sign in methods, MCP support and how hard they are to connect. You still spot check the findings before trusting them.

  • Workflow builder by chat

    Builds automation workflows from plain language instructions instead of dragging nodes by hand. You review and test each workflow before turning it on.

  • Meeting notes to issues

    Turns meeting notes into draft issues and specs so follow ups do not get lost. You review the list before anything is filed.