0
/ 100
Early stage. Tests, CI, and a strong README would raise this score quickly.
A CLI tool for enforcing determinism in LLM development workflow automation.
A low grade is a to-do list, not a judgment of your code
Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to B (80).
See your top fixesTop fixes
Highest-impact changes first, ranked by point weight
- 1CI/CD14pt
Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.
- 2CI/CD14pt
Add `pull_request:` to the workflow `on:` triggers.
- 3CI/CD14pt
Add a lint step to catch style issues automatically.
- 4CI/CD14pt
Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
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
52
No license detected.
→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.
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.
Engineering
68
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/release.yml).
Lockfile present (package-lock.json). Installs are reproducible.
Test files detected (src/commands/backlog/acquireLock.test.ts).
Linter or formatter configured (devDependency in package.json).
Project health
92
Dependency manifest found (package.json).
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)
- 1Forks
- 508Releaseslatest 6mo ago
Community
- -Community health
- -authors own >50% of commits
- 6Watchers
Responsiveness
- <1hMedian issue response
- -Median PR merge time
- 2Open issues
Repository files28 root entries
- .assist
- .claude
- .githubGood: CI is configured (.github/workflows/release.yml).
- .vscode
- claude
- netcap-extension
- oxlint-rules
- srcGood: Test files detected (src/commands/backlog/acquireLock.test.ts).
- .gitattributes
- .gitignoreGood: .gitignore present.
- .node-versionGood: Environment pinned via .node-version.
- .oxfmtrc.json
- .oxlintrc.json
- .releaserc.json
- allowed.cli-reads
- allowed.cli-writes
- assist.yml
- CHANGELOG.md
- CLAUDE.md
- knip.json
- package-lock.jsonGood: Lockfile present (package-lock.json). Installs are reproducible.
- package.jsonGood: Dependency manifest found (package.json).
- PROGRESS.md
- README.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.
- refactor.yml
- STT_PLAN.md
- tsconfig.json
- tsup.config.ts
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/staff0rd/assist)