Skip to content

Scope, fee and working days are published on every engagement

CorePhysix Labs Technology lab

Specification ADV·109

ADV · Tech Advisory Defined scope Fixed fee

Single Pull Request Review

One pull request of up to 400 changed lines reviewed with line-level comments and a merge verdict, so a risky change gets a proper check.

Fee · GST incl.
₹400
Duration
2 working days
Deliverables
5

01 Overview

Small teams often have nobody available to review the changes that matter most. Add our reviewer to the pull request or send a patch, and an engineer reviews it in a fixed order: correctness, then unhandled failure cases, then structure, then the minor points. Comments go directly on the diff with a short verdict on whether to merge, and each is marked as blocking or a matter of taste. This is a review, not a rewrite.

02 Deliverables

5 items

What you receive at handover

  1. D01 Line-level comments on one pull request of up to 400 changed lines
  2. D02 A summary verdict: merge, merge with changes, or not ready to merge
  3. D03 Each comment labelled as blocking, worth doing, or a matter of preference
  4. D04 Specific failure cases the change does not appear to handle
  5. D05 A note on any test worth adding before the change ships

03 Outcomes

What should be true once it ships

  • An independent review of a critical change without hiring for it
  • Failure cases caught before they reach your users
  • Feedback your developer can act on in the tool they already use

04 Process

How the 4 stages run

  1. Invite You add our reviewer to the repository or send a patch file
  2. Read An engineer reviews the diff and enough surrounding code to judge it
  3. Comment Feedback is left on the pull request itself, not in a separate document
  4. Reply We respond once to your replies on the thread, so it works as a conversation

05 Fit & inputs

A good fit for

  • Solo developers and small teams without an experienced reviewer
  • Teams shipping an unusually risky change, such as payments or authentication
  • Founders who want an independent check on contractor code before merging

What we need from you

  • Repository access for one reviewer, or a patch file with enough context to follow
  • A sentence or two on what the change is supposed to achieve

These inputs are collected through the technical brief in your dashboard after payment. The duration is counted from when they arrive.

06 Answers

Questions about this engagement

Tell us the size first. We will confirm it fits or suggest splitting it, and we will not quietly skim a larger change.

In yours, through a reviewer account you create and can revoke. We do not clone your code to keep.

Not under this engagement. We comment and your team commits. Ask separately if you want the fixes written.

This is technology work delivered digitally — nothing is shipped. Work is delivered into systems you control within the duration stated above, and the delivery and refund policies set out what happens if a date is missed.

REL Related

Often considered alongside.

All Tech Advisory

Codebase Health Snapshot

Half a day reading your repository, then a short candid report on its condition and top three risks, before you hire, buy or rewrite.

Written report of 3 to 4 pages, without padding

Fixed fee · GST incl.

₹1,999

Duration

4 working days

Is This Quote Reasonable

Forward a development quote and its scope for a written verdict on price and gaps, plus the questions to ask before you sign.

A written verdict on whether the price is low, fair or high for the scope described

Fixed fee · GST incl.

₹200

Duration

2 working days

Cloud Bill Sanity Check

An engineer reads one month of your cloud bill and names the five most questionable charges with estimated savings, so waste is cut quickly.

Review of one month of billing data from your cloud provider

Fixed fee · GST incl.

₹999

Duration

3 working days

GST included

₹400

Next step

Have a system that needs building, fixing or securing?