0
/ 100
Good shape overall. A few tweaks would push it into the top tier.
Exercism exercises in Ruby.
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.
- 2README12pt
Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
- 3README12pt
Add CI/build status badges from shields.io or your CI provider to signal project health.
- 4Install and run instructions9pt
Add a section showing how to start or use the project.
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
62
Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).
→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
79
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.
Test files detected (exercises/concept/amusement-park-improvements/attendee_test.rb).
Lockfile present (Gemfile.lock). Installs are reproducible.
CI is configured (.github/workflows/exercise-tests.yml).
Ruby linting configured (.rubocop.yml).
Project health
100
Dependency manifest found (Gemfile).
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)
- 530Forks
- 0Releases
Community
- -Community health
- -authors own >50% of commits
- 597Watchers
Responsiveness
- 8hMedian issue response
- 3hMedian PR merge time
- 12Open issues
Repository files23 root entries
- .appends
- .githubGood: CI is configured (.github/workflows/exercise-tests.yml).Good: Dependabot configured for github-actions.
- bin
- concepts
- docs
- exercisesGood: Test files detected (exercises/concept/amusement-park-improvements/attendee_test.rb).
- generatorv2
- lib
- reference
- test
- .gitignoreGood: .gitignore present.
- .rubocop.ymlGood: Ruby linting configured (.rubocop.yml).
- .ruby-versionGood: Environment pinned via .ruby-version.
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- config.json
- exercise-concepts.todo.json
- GemfileGood: Dependency manifest found (Gemfile).
- Gemfile.lockGood: Lockfile present (Gemfile.lock). Installs are reproducible.
- LICENSEGood: Licensed under MIT.
- package.json
- Rakefile
- 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.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- yarn.lock
Add this badge to your README
It updates automatically each time the repo is re-graded.
[](https://www.repo-grade.com/report/exercism/ruby)