Skip to content

README.md

Latest commit

 

History

History
112 lines (71 loc) · 3.65 KB

README.md

File metadata and controls

112 lines (71 loc) · 3.65 KB

Small GitHub PR Sprint

Focused public-repo fixes delivered as a clean pull request or patch file.

Built for maintainers, indie builders, and OSS projects that have small annoying GitHub issues they want solved without hiring a freelancer, joining a call, or giving private access.

For the small fixes nobody wants to lose half a day on: open a request, get a focused PR or patch, and pay only after the sprint is accepted and priced.

What this is good for

  • Documentation fixes
  • Broken links
  • README / install notes
  • Small examples
  • Tiny test improvements
  • Regression tests for public issues
  • Small public bug fixes with clear expected behavior

Good-fit requests

Good requests are specific, public, and verifiable:

  • “Fix this broken README install command.”
  • “Add a regression test for this public issue.”
  • “Update docs after this CLI flag changed.”
  • “Fix this example so it passes the documented command.”
  • “Open a PR correcting broken links and setup instructions.”

See example sprint requests for more accepted/rejected examples.

Bad requests:

  • “Fix my app.”
  • “Improve the architecture.”
  • “Make all tests pass” with no failing command or expected behavior.
  • Private repositories, credentials, production access, auth/payment/wallet logic, security exploit work, scraping/ToS-risk work, private APIs, mobile/hardware-only testing, spam/outreach, or vague refactors.

Pricing

Launch pricing for early requests:

  • $10 — docs, links, README/install notes, tiny examples
  • $25 — tiny test improvement, regression test, or very small bug fix with clear verification
  • $50+ — bounded public bug fix after review

Final price is confirmed after the request is reviewed.

Please do not send payment before the request is accepted and priced.

I may decline requests that are too vague, too risky, too large, not reproducible, or not a good fit for a fixed-scope sprint.

Delivery

Accepted requests are delivered as:

  1. A focused pull request, or
  2. A patch file if external PRs are not accepted

Each delivery includes a short verification note explaining:

  • What changed
  • Which files were touched
  • How the change was checked
  • Any limitations or follow-up notes

Target turnaround is usually 24–72 hours after acceptance, depending on scope, repo complexity, and queue.

How to request a sprint

Open an issue in this repo with:

  1. Public GitHub repo URL
  2. Issue URL or exact problem statement
  3. Expected behavior
  4. Current behavior
  5. Acceptance criteria
  6. Test command or verification path, if known
  7. Whether external PRs are accepted, or whether patch-file delivery is OK
  8. Preferred pricing tier
  9. Urgency / deadline, if any

Please wait for scope confirmation before sending payment. I will reply with the fixed scope, price, ETA, and verification plan first.

Payment

Payment is accepted in USDC on Base, Arbitrum, Linea, or Ethereum.

Preferred low-fee networks: Base or Arbitrum.

Wallet:

0x23151Ef76ae6404f0a5fF4FE3dd3551a4f563125

Please confirm the network before sending.

Buyer covers network fees. Do not send other assets unless explicitly agreed.

If you prefer a bounty-platform flow, create an Algora or Opire bounty for the GitHub issue and link it in your request.

Marketplace copy

If you want to share this offer in a marketplace or public channel where fixed-price technical help is welcome, use MARKETPLACE-LISTING.md.

Response templates

For accepted, needs-narrowing, decline, delivery, and payment wording, see RESPONSE-TEMPLATES.md.

Status

Accepting small public GitHub fix requests.