Not Quite My Tempo Client Repo Onboarding (.fletcher.json Setup) (Onboarding)

Not Quite My Tempo Client Repo Onboarding (.fletcher.json Setup) (Onboarding)

1. 01

   Install the Fletcher GitHub App on a sandbox repository first

   Create an internal repo and install the app there so your delivery team sees the roughly one minute review cycle, line-by-line comments, and severity flags before any client repo is touched.

2. 02

   Confirm the Gemini key arrangement with the client

   Decide whether reviews run on Fletcher's keys (200 review credits a month on Fletcher Pro) or the client's own Gemini API key. Reviews on the client's own key never consume credits, which keeps retainer cost predictable.

3. 03

   Draft the .fletcher.json for the client repository

   Set severity threshold, review intensity, tone, ignore globs, and repository guidelines. Keep the first version narrow so the client's team is not flooded on their first pull request.

4. 04

   Add AGENTS.md or CLAUDE.md to the repo

   Fletcher reads repository guidelines and dependency manifests for context-aware analysis. Without these files the review comments lack project context and read as generic linting.

5. 05

   Validate output against known code issues

   Push a pull request containing defects the client already knows about and check that severity flags land on the right lines. Tune the .fletcher.json until the critical flags match what a senior reviewer would catch.

6. 06

   Document the retry path for the client team

   Show them that commenting /fletcher again on a pull request retries a failed review. Put this in the handoff note so nobody files a support ticket over a stalled review.

7. 07

   Hand off with a written review workflow

   Deliver the config file, the key arrangement, and the retry instructions as one document. Note that pull request comments carry Fletcher branding, so the client should expect the tool name in their review thread.