Good shape overall. A few tweaks would push it into the top tier.
Meta-prompting, context engineering, and centralized instructions management for AI coding agents
Documentation
92
Contributing guide is detailed and thorough.
README documents how to install the project.
README is present.
Licensed under Apache-2.0.
Engineering
55
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 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/validate-test-cases.yml).
Test files detected (.github/scripts/test_load_stories.py).
Lockfile present (requirements.txt). Installs are reproducible.
Project health
100
Dependency manifest found (requirements.txt).
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)
- 60Forks
- 174Releaseslatest 3mo ago
Community
- —Community health
- —authors own >50% of commits
- 307Watchers
Responsiveness
- <1hMedian issue response
- <1hMedian PR merge time
- 11Open issues
Repository files41 root entries
- .agents
- .claude
- .claude-plugin
- .cursor-plugin
- .githooks
- .githubGood: Test files detected (.github/scripts/test_load_stories.py).Good: CI is configured (.github/workflows/validate-test-cases.yml).
- agents
- docs
- instructions
- plans
- plugins
- scripts
- srcGood: Environment pinned via src/ims-mcp-server/Dockerfile.
- test-library
- .cursorignore
- .gitignoreGood: .gitignore present.
- CHANGELOG.md
- CONFIGURATION.md
- CONTRIBUTING.mdGood: 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.Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).Good: Contributing guide describes the PR/review workflow.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- DEPLOYMENT_GUIDE.md
- DEVELOPER_GUIDE.md
- ELEVATOR_SPEECH.md
- FAQ.md
- gain.json
- INSTALLATION.md
- LICENSEGood: Licensed under Apache-2.0.
- llms-full.txt
- MCPs.md
- mypy.ini
- NOTICE
- OVERVIEW.md
- PLUGINS.md
- QUICKSTART.md
- 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.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.
- requirements.txtGood: Lockfile present (requirements.txt). Installs are reproducible.Good: Dependency manifest found (requirements.txt).
- REVIEW.md
- run-tests.sh
- SECURITY.mdGood: Security policy present.
- TROUBLESHOOTING.md
- USAGE_GUIDE.md
- validate-types.sh