Proof hub / Repo review sample

Turn a failing repo, issue, or CI run into a clear fix plan.

Goal: give the buyer one concise diagnosis, the exact failing command or check, the likely cause, and the smallest repair path that can be implemented or handed to their team.

1. Start with the repo contract

The first pass should identify the repo URL, issue link, failing command, runtime versions, expected behavior, current error output, and whether the buyer wants a review note, a patch, or a handoff plan. Public repos or buyer-approved private access only.

2. Use one review record

{
  "review_id": "repo_review_20260523_001",
  "repo": "sample-org/sample-app",
  "surface": "GitHub Actions",
  "failing_check": "test",
  "command": "npm test",
  "error_class": "dependency version mismatch",
  "impact": "pull requests cannot merge",
  "next_step": "pin dependency and rerun focused tests",
  "status": "ready_for_buyer_review"
}

3. Build the first paid slice

  • Reproduce the failing command or read the failing check output.
  • Separate environment problems from code problems.
  • List the smallest likely repair and the acceptance command.
  • Flag risky changes that need maintainer review before implementation.
  • Deliver a short note the buyer can paste into an issue, PR, or task.

4. Acceptance checks

  • The failing surface is named precisely: local command, CI check, install step, dependency, or docs gap.
  • The buyer can see what was reproduced and what was inferred.
  • The recommended fix is small enough for a first paid task.
  • No credentials, secret logs, private tokens, or account screenshots are required.