0
/ 100
Strong early engineering with some momentum.
Top fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 2CI/CD14pt
Add a lint step to catch style issues automatically.
- 3CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
- 4CI/CD14pt
Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
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
70
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
87
CI is configured (.github/workflows/release.yml).
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (packages/shared-skills/skills/ast-grep/tests).
Linter or formatter configured (packages/shared-skills/skills/programming/scripts/go/templates/.editorconfig).
Issue or PR templates present.
Project health
84
No repository description set on GitHub (−60 pts).
→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.
Dependency manifest found (package.json).
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- -Commits (30d / 90d)
- 0Forks
- 1Releaseslatest 1mo ago
Community
- -Community health
- -authors own >50% of commits
- 10Watchers
Responsiveness
- -Median issue response
- <1hMedian PR merge time
- 0Open issues
Repository files20 root entries
- .githubGood: CI is configured (.github/workflows/release.yml).Good: Issue or PR templates present.
- .persona
- docs
- packagesGood: Test files detected (packages/shared-skills/skills/ast-grep/tests).Good: Linter or formatter configured (packages/shared-skills/skills/programming/scripts/go/templates/.editorconfig).
- scripts
- src
- tests
- .gitignoreGood: .gitignore present.
- .npmignore
- CHANGELOG.md
- LICENSEGood: Licensed under Apache-2.0.
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- README.ja.mdGood: README is present.Good: README is well structured with multiple sections.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.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.
- README.ko.md
- README.md
- README.zh-cn.md
- tsconfig.build.json
- tsconfig.json
- vitest.config.ts
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/jyt6640/persona-harness)