Getting some notice. Tests and CI would be the fastest wins.

Clownfish is a maintainer codex harness for resolving clusters of issues identified in bulk at scale. ๐Ÿ 

Documentation

54

License6pt0

No license detected.

โ†’ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt0

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.

README12pt70

README is present.

Install and run instructions9pt100

README documents how to install the project.

Engineering

46

Linting and formatting5pt0

No linter or formatter config found.

โ†’ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

Reproducibility6pt0

No dependency lockfile found (โˆ’70 pts).

โ†’ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

Issue and PR templates6pt0

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/CD14pt57

CI is configured (.github/workflows/cluster-batch.yml).

Tests18pt80

Test files detected (test).

Project health

100

Dependency manifest6pt100

Dependency manifest found (package.json).

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)
  • 18
    Forks
  • 0
    Releases

Community

  • โ€”
    Community health
  • โ€”
    authors own >50% of commits
  • 56
    Watchers

Responsiveness

  • 1d 22h
    Median issue response
  • <1h
    Median PR merge time
  • 2
    Open issues
Repository files17 root entries
  • .agents
  • .github
    Good: CI is configured (.github/workflows/cluster-batch.yml).
  • .projectclownfish
  • docs
  • instructions
  • jobs
  • prompts
  • results
  • schemas
  • scripts
  • test
    Good: Test files detected (test).
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • apply-report.json
  • package.json
    Good: Dependency manifest found (package.json).
  • README.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.
    Issue: No live demo link in the README (โˆ’20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.
    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.