I fix focused repo problems for maintainers and small teams: failing tests, broken CI, TypeScript errors, dependency regressions, small backend bugs, cache failures, and missing regression tests.
I also maintain Maintainer Radar, a local-first PR triage tool for maintainers dealing with noisy review queues: https://github.com/JackSpiece/maintainer-radar
It can recommend the next maintainer workflow before you install anything locally:
maintainer-radar recommend https://github.com/owner/repo/pulls
It also ships as a reusable GitHub Action and can bootstrap a read-only queue report with:
maintainer-radar init-action --path .github/workflows/maintainer-radar.yml
I can also set it up for maintainers as a small fixed-scope service: add the read-only workflow, tune the config profile and first report, and leave a short handoff note with the recommended workflow, attention level, and next-session digest.
Try the no-install browser preview on a public repo: https://jackspiece.github.io/maintainer-radar/
Example scan: https://jackspiece.github.io/maintainer-radar/?repo=python/cpython
Request a focused fix: https://github.com/JackSpiece/JackSpiece/issues/new?template=fix-request.yml
Best fit:
- JavaScript and TypeScript
- Python
- Rust
- Node, React, API code
- GitHub Actions and CI failures
- Test coverage for known bugs
Good projects are scoped and verifiable: a failing command, a clear bug report, a broken workflow, or a small behavior gap with expected output.
Typical fixed-scope pricing:
- Diagnosis: $25 for one failing command, log review, and a written fix plan.
- Queue triage setup: $50 for one Maintainer Radar workflow, first report, and handoff note.
- Focused fix: $75 for one small bug, CI failure, or typecheck/lint breakage.
- Priority fix: $150 for one issue with focused tests and a verification note.
Payment can be handled through an agreed marketplace, milestone, or escrow path before delivery. Do not send production secrets.
More detail: https://github.com/JackSpiece/JackSpiece/blob/main/SERVICES.md
How I work:
- Reproduce the failure or inspect the target behavior.
- Make the smallest practical fix.
- Run the relevant test, lint, or build command.
- Send a PR or patch with a short root-cause note.
Public proof points:
- Maintainer triage tooling with browser preview: https://github.com/JackSpiece/maintainer-radar
- Browser data edge case: sitespeedio/chrome-har#157
- Python cache reliability: langflow-ai/langflow#13167
- TypeScript config hardening: openclaw/openclaw#83296
- GitLab LFS media handling: decaporg/decap-cms#7815
- Rust test coverage and performance slices: https://github.com/spaceandtimefdn/sxt-proof-of-sql/pulls?q=is%3Apr+author%3AJackSpiece
Typical small fixed-scope work:
- Diagnose one failing command or CI job
- Recommend the next maintainer workflow for an active PR queue
- Set up a read-only Maintainer Radar PR queue report with a tuned config profile
- Fix one focused bug and add a regression test when practical
- Clean up a dependency or typecheck breakage
- Patch a small backend reliability issue
- Add focused test coverage around known behavior
Send a repo link, failing command or log, and the expected behavior.