agent-ready is now on npm: one command to check AI coding agent readiness

[EShener]

agent-ready is now published on npm and has a one-command quick start for checking repository readiness for AI coding agents.

npx --yes @eshen_fox_mie/agent-ready improve --preset team --dry-run

What it does:

• scans a repository for languages, package manager, commands, CI, README, and agent docs
• gives an explainable Agent Readiness Score
• generates a canonical AGENTS.md plus small shims for Claude Code, Cursor, Gemini CLI, and GitHub Copilot
• creates CI annotations, Step Summary output, PR comments, snapshots, leaderboards, and cleanup roadmaps
• supports oss, team, and enterprise presets for faster setup

Useful links:

• npm: https://www.npmjs.com/package/@eshen_fox_mie/agent-ready
• Showcase: https://github.com/EShener/agent-ready/blob/main/docs/showcase.md
• Examples: https://github.com/EShener/agent-ready/blob/main/docs/examples/README.md
• Growth playbook: https://github.com/EShener/agent-ready/blob/main/docs/growth-playbook.md

I am especially looking for feedback on missing framework detectors and readiness rules. If your repo needs Next.js, Astro, SvelteKit, Rails, Django, Docker Compose, generated SDK, or monorepo-specific support, please reply here or open an issue.

[EShener]

Shipped another adoption-focused update on main: real framework and local-service detection now has fixture coverage.\n\nWhat changed:\n- Next.js detection now recognizes dependencies, next.config files, App Router files, and pages router files.\n- Astro detection now recognizes astro.config files and .astro source files, not only package dependencies.\n- Docker and Docker Compose are now surfaced as tooling signals, with generated AGENTS.md guidance for local services.\n- Generated instructions now keep useful custom commands such as services and services:stop.\n\nVerified locally with npm run check and npm test: 72 passing.\n\nThis makes agent-ready more useful on real app repositories where framework signals and local dependencies are often split across files instead of living only in package.json.

[EShener]

Progress update: the project now has more real-repo coverage and a clearer contributor path.\n\nShipped on main today:\n- stronger Next.js and Astro detection with fixtures\n- Docker and Docker Compose detection with generated local-service guidance\n- real-world readiness snapshots in the examples gallery\n- weekly growth metrics tracking with collection commands\n\nCI is green on main. I also opened three newcomer-friendly issues for more detectors and public-reference examples: #12, #13, and #14.\n\nTry the examples gallery:\n\nbash\nnpx --yes @eshen_fox_mie/agent-ready examples\n\n\nOr preview a repo-specific improvement plan:\n\nbash\nnpx --yes @eshen_fox_mie/agent-ready improve --preset team --dry-run\n

[EShener]

Progress update: detector coverage expanded again.\n\nNew on main:\n- SvelteKit and Nuxt detection from configs, route conventions, and .svelte / .vue files\n- Rails and Laravel detection with Bundler and Composer command inference\n- Real-world snapshot examples for SvelteKit, Nuxt, Rails, and Laravel\n\nCI is green on main and local tests are at 74 passing.\n\nThe next useful contribution paths are now tracked in #15, #16, and #17. The only release blocker is still npm automation in #11, so npm latest remains 0.1.24 while main has the newest detector work.

[EShener]

Progress update: main now covers more backend ecosystems and has clearer detector documentation.\n\nNew on main:\n- Spring Boot detection with Maven and Gradle wrapper commands\n- detector coverage docs grouped by ecosystem\n- Ruby/PHP package manager edge cases for hybrid frontend/backend apps\n\nCI is green on main and local tests are at 76 passing.\n\nNew contribution paths are tracked in #18, #19, and #20. npm latest is still 0.1.24 until #11 is resolved, so the newest detector work is currently on main but not yet on npm.

[EShener]

Progress update: main now has .NET/C# support and release prep for v0.1.26.\n\nNew on main:\n- .NET/C# detection with dotnet restore, dotnet build, and dotnet test inference\n- Go Gin and Rust workspace web fixture coverage\n- draft v0.1.26 release notes\n- npm Trusted Publishing-oriented workflow and setup docs\n\nCI is green on main and local tests are at 78 passing. npm latest is still 0.1.24 until the npm Trusted Publisher is configured and the next release is published.\n\nNew contribution paths: #21, #22, and #23.