A written review of one repo or PR set.
I read the agreed repository or pull-request set and write what is wrong, what is load-bearing, and what I would not ship yet. I do not rewrite the product in this engagement.
$185
Written review of one repo or PR set.
Request a fit checkNo-charge fit check before access or work. If it fits, the fixed scope and price are confirmed first.
Stages
Open each stage to see the work product. The exact scope is set only after the evidence is reviewed.
Bound the readName the repo or PR set and the question.
Confirm the repository, the pull requests, the language, and the decision the review has to support. Work does not start until that bound is agreed.
Output: the agreed review bound.
ReadInspect the agreed source.
Read the named source and note defects, load-bearing behavior, and anything I would not ship yet. I stay inside the bound.
Output: a working list of findings with evidence.
WriteDeliver the review.
Write the findings. Each one names the evidence. I do not silently start rewriting the product; that is a different service.
Output: one written review plus one named revision pass.
What is included
- One repository or one agreed pull-request set
- A written review: defects, load-bearing pieces, and what I would not ship yet
- One named revision pass on the written review
I do not promise App Review approval, ranking, downloads, or revenue. The written scope decides the work.
Fit
Good fit
I read the agreed repository or pull-request set and write what is wrong, what is load-bearing, and what I would not ship yet. I do not rewrite the product in this engagement.
I scope the work, review what ships, and you own the source.
Not included
- Implementation, a rewrite, or unbounded pairing
- Android review, legal advice, or security-certification claims
- App Review approval or ranking promises
Request
Request a fit check
Send the project name, the repository or PR set, and the decision you need the review to support. I will reply with whether it fits this engagement.
Do not submit passwords, API keys, tax or identity documents, or private customer data. Sensitive access is never requested in the first message.