clacky-ai/openclacky

0

/ 100

Documentation93
Engineering86
Health100
Ruby1,039MIT1d ago
Grade a repo

A well-known project done right. Strong docs and solid engineering throughout.

The most Token-efficient open-source AI Agent

Documentation

93

Contributing guide5pt72

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

86

Tests18pt80

Test files detected (benchmark/fixtures/sample_project/spec).

Reproducibility6pt80

Lockfile present (Gemfile.lock). Installs are reproducible.

CI/CD14pt85

CI is configured (.github/workflows/main.yml).

Linting and formatting5pt100

Ruby linting configured (.rubocop.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (Gemfile).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 87
    Forks
  • 108
    Releaseslatest 4mo ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,039
    Watchers

Responsiveness

  • 7h
    Median issue response
  • 2h
    Median PR merge time
  • 34
    Open issues
Repository files30 root entries
  • .clacky
  • .github
    Good: CI is configured (.github/workflows/main.yml).
    Good: Issue or PR templates present.
  • benchmark
    Good: Test files detected (benchmark/fixtures/sample_project/spec).
  • bin
  • clacky-legacy
  • docs
  • homebrew
  • lib
  • scripts
  • sig
  • spec
  • .clackyrules
  • .gitignore
    Good: .gitignore present.
  • .rspec
  • .rubocop.yml
    Good: Ruby linting configured (.rubocop.yml).
  • CHANGELOG.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • Gemfile
    Good: Dependency manifest found (Gemfile).
  • Gemfile.lock
    Good: Lockfile present (Gemfile.lock). Installs are reproducible.
  • Gemfile.lock.ruby-2.6
  • Gemfile.lock.ruby-3.3
  • Gemfile.lock.ruby-4.0
  • LICENSE.txt
    Good: Licensed under MIT.
  • openclacky.gemspec
  • Rakefile
  • README_CN.md
    Good: 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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • README.md
  • ROADMAP.md