0
/ 100
Strong early engineering with some momentum.
Control your Pi coding agent from your phone. Pair with a one-time QR code and chat with your local agent — even when you're away from your computer.
Top fixes
Highest-impact changes first, ranked by point weight
- 1Tests18pt
Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.
- 2CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 3CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 4CI/CD14pt
Add a lint step to catch style issues automatically.
Working through the fixes? Let every push regrade itself.
The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.
Scorecard
Every check, grouped by category and sorted worst-first
Documentation
89
CONTRIBUTING guide found.
README is present.
README documents how to install the project.
A license file is present.
Engineering
61
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
CI is configured (.github/workflows/app-release.yml).
Test files detected (app/ios/RunnerTests/RunnerTests.swift).
Lockfile present (pi-extension/pnpm-lock.yaml). Installs are reproducible.
Linter or formatter configured (site/eslint.config.mjs).
Project health
100
Dependency manifest found (app/android/app/build.gradle.kts).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 16Forks
- 7Releaseslatest 1mo ago
Community
- -Community health
- -authors own >50% of commits
- 67Watchers
Responsiveness
- 2hMedian issue response
- 9hMedian PR merge time
- 0Open issues
Repository files18 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/app-release.yml).
- .orchestration
- appGood: A license file is present.Good: Test files detected (app/ios/RunnerTests/RunnerTests.swift).Good: Dependency manifest found (app/android/app/build.gradle.kts).
- branding
- cockpitGood: CONTRIBUTING guide found.Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
- pi-extensionGood: Lockfile present (pi-extension/pnpm-lock.yaml). Installs are reproducible.
- plan
- relayGood: Environment pinned via relay/Dockerfile.
- review
- rp-s3
- scripts
- siteGood: Linter or formatter configured (site/eslint.config.mjs).
- .gitignoreGood: .gitignore present.
- CHANGELOG.md
- CLAUDE.md
- PROTOCOL.md
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Good: README has code examples.Good: README links to a live demo or deployed app.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Good: README documents how to install the project.Good: README documents how to run the project.
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/jacobaraujo7/remote_pi)