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
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
46
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.
No dependency lockfile found (โ70 pts).
โ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.
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/cluster-batch.yml).
Test files detected (test).
Project health
100
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)
- 18Forks
- 0Releases
Community
- โCommunity health
- โauthors own >50% of commits
- 56Watchers
Responsiveness
- 1d 22hMedian issue response
- <1hMedian PR merge time
- 2Open issues
Repository files17 root entries
- .agents
- .githubGood: CI is configured (.github/workflows/cluster-batch.yml).
- .projectclownfish
- docs
- instructions
- jobs
- prompts
- results
- schemas
- scripts
- testGood: Test files detected (test).
- .env.example
- .gitignoreGood: .gitignore present.
- AGENTS.md
- apply-report.json
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: 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.