← ClaudeAtlas

ai-readylisted

Use only when the user asks to make the repo AI-ready or AI-optimized (AGENTS.md migration, debugging/testing setup, docs). Do not run on your own.
kargnas/skills · ★ 6 · AI & Automation · score 66
Install: claude install-skill kargnas/skills
# Make this project AI-ready When starting, let the user know in one line that this skill is being used. Goal: Enhance outdated AI Rule file and the codebase in this project to up-to-date AI Rule file and AI-ready easy setting with up-to-date codebase understanding. When this project is mono-repo and has multiple projects (with packages.json, composer.json, ...): - Ensure having AGENTS.md in every project's root, separated from the root AGENTS.md - Ensure having .env.example in every project's root, separated from the root .env.example - Ensure having .env.ai-ready in every project's root, separated from the root .env.ai-ready 1. Update .gitignore - AGENTS.md and AI Agent rules shouldn't be in .gitignore - Check if AGENTS.md, CLAUDE.md, .cursorrules or any other AGENT related files are in `.gitignore` - If they are, remove those lines from `.gitignore` - Stash the AGENTS files if it's existing - Commit the `.gitignore` change - Then restash the AGENTS files - Explain (easily) to the users why the AGENTS.md shouldn't be in `.gitignore`. - Add missing ignore files - `.env` - `.env.*` - `!.env.ai-ready` - `!.env.example` - `.sisyphus/` - `.sisyphus/boulder.json` - `!.sisyphus/.gitignore` - `!.sisyphus/plans/` - `!.sisyphus/evidence/` - (and more you think it's needed...) 2. Migrate from CLAUDE.md to AGENTS.md 1. If this project has CLAU