Implementation BlueprintExecution layer

Not Quite My Tempo PR Review Retainer Setup (5-7 days)

Agencies install and configure Not Quite My Tempo on a client's GitHub repository, tune .fletcher.json for severity and scope, and hand off a documented automated PR review workflow that runs on the client's own Gemini API key. Time: 5-7 days.

By InnovaAI ResearchPublished

AI Code Tools

How do you implement it?

Blueprint

Not Quite My Tempo PR Review Retainer Setup (5-7 days)

Agencies install and configure Not Quite My Tempo on a client's GitHub repository, tune .fletcher.json for severity and scope, and hand off a documented automated PR review workflow that runs on the client's own Gemini API key.

Prerequisites
  • Client GitHub organization admin access to install the Fletcher GitHub App
  • A Google Gemini API key provisioned under the client's own Google Cloud account
  • One active repository with at least three recent pull requests to use as a calibration set
  • Agreed severity threshold and review tone documented in a signed scope note
  • Agency engineer with GitHub Actions and JSON configuration experience
Execution Timeline
  • 1.Create an internal sandbox repository and install the Fletcher GitHub App on it
  • 2.Open, reopen, and push to test pull requests to observe the roughly one minute review cycle
  • 3.Record line-by-line comment format and severity flags for the client kickoff deck
  • 1.Draft the first .fletcher.json for the client repository with severity threshold, intensity, tone, and ignore globs
  • 2.Add AGENTS.md or CLAUDE.md so Fletcher reads repository guidelines and dependency manifests
  • 3.Run a review on a known-buggy branch and compare output against the team's expected findings
  • 1.Install the Fletcher GitHub App on the client repository and confirm webhook delivery
  • 2.Set the Gemini API key under the client's own account so usage costs stay on their bill
  • 3.Trigger a review on a live pull request and verify the /fletcher retry command works
  • 1.Tune .fletcher.json severity rules against three historical pull requests from the calibration set
  • 2.Adjust ignore globs to exclude generated files and vendored dependencies
  • 3.Document the review scope and escalation path for critical severity findings
  • 1.Run a parallel review week where Fletcher comments alongside a human reviewer on every PR
  • 2.Collect false positives and missed issues into a tuning log
  • 3.Update .fletcher.json intensity and tone based on the tuning log
  • 1.Write the client runbook covering PR triggers, the /fletcher retry command, and severity triage
  • 2.Record a 10 minute walkthrough of the Fletcher comment thread for the client engineering team
  • 3.Hand off repository access and the .fletcher.json file to the client's designated maintainer
  • 1.Hold a 30 minute review of the first week's Fletcher findings with the client team
  • 2.Agree the monthly retainer scope for ongoing .fletcher.json tuning and severity reporting
  • 3.Archive the sandbox repository and close the setup engagement
$1,800 setup fee for the 16 hour Starter engagement, plus Fletcher Pro workspace pricing quoted by sales for the client's review credit volume; reviews on the client's own Gemini key never consume Fletcher credits5-7 days
ROI Logic

The Starter offer bills $1,800 for 16 hours of setup, roughly $112 per hour, while the client carries the Gemini API usage on their own key and Fletcher Pro workspace pricing is quoted per workspace by sales. The agency margin comes from configuration and tuning labor, not from reselling review credits, so a monthly tuning retainer can be layered on top without touching the tool's per-workspace bill.

Deliverables
  • Client-specific .fletcher.json with severity threshold, intensity, tone, and ignore globs
  • AGENTS.md or CLAUDE.md file wired into the repository for context-aware reviews
  • PR review runbook covering triggers, the /fletcher retry command, and severity triage
  • Tuning log comparing Fletcher findings against human reviewer output over one week
  • Handoff recording and signed retainer scope for ongoing configuration maintenance
Definition of Done

The client repository has Fletcher installed, a tuned .fletcher.json committed, and one full week of pull requests reviewed with severity flags triaged by the client's own maintainer.

Open the Not Quite My Tempo courseNot Quite My Tempo decision recordBrowse the Academy

More on Not Quite My Tempo

More for AI Code Tools