Is the Legacy To AI Ready skill free?

Yes. The skill itself is free from nicepkg/ai-workflow. SkillProof publishes the install command and an independent test verdict at no cost.

What is the Legacy To AI Ready SkillProof Score?

8.8/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 7/10, docs & honesty 5/5.

How do I install Legacy To AI Ready?

Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.

Can I use Legacy To AI Ready with Cursor, Copilot, Gemini CLI, Codex or other AI tools?

The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.

Legacy To AI Ready

Analyzes an existing codebase and generates CLAUDE.md and Claude Code config

by nicepkg · nicepkg/ai-workflow

Tested · Works

Install — copy the command Download source ↗

Test report

Verdict: Tested · Works
Score: 8.8/10
Tested: Jul 31, 2026
Environment: Claude Code 2.x (agent harness)
Upstream re-checked: Aug 10, 2026 · 5cbf05c

Fetched SKILL.md (frontmatter parses, name+description present) and spot-checked 4 referenced files raw: analyze_codebase.py, claude-md-patterns.md, resource-discovery.md, CLAUDE.md.template all HTTP 200. Ran the 969-line analyze_codebase.py (syntax OK, only stdlib; sole subprocess call is `git log` to detect commit patterns, no exfiltration/curl|sh) against a real TS test project I built: it correctly detected TypeScript/Jest/ESLint/Prettier, extracted build/test/lint scripts, flagged conventional-commits from git history, warned about .env, and recommended a commit.md command. Wrote a baseline CLAUDE.md from general knowledge vs a skill-followed one using the script output + template: the skill version uniquely captured the conventional-commit convention, the .env/.claudeignore security note, prettier config values, and a follow-up commands recommendation the baseline entirely missed.

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

Installs cleanly 5/5
Triggers reliably 5/5
Output vs. baseline 7/10
Docs & honesty 5/5

What Legacy To AI Ready does

Scans a legacy codebase with a bundled Python analyzer to detect languages, frameworks, build/test/lint commands, git commit conventions and sensitive files, then generates Claude Code configuration (CLAUDE.md, rules, agents, commands, hooks). Triggers when a user wants to make an existing project AI-ready, generate a CLAUDE.md, or set up Claude Code coding standards for a repo.

How to install Legacy To AI Ready

git clone --depth 1 https://github.com/nicepkg/ai-workflow.git /tmp/legacy-to-ai-ready-src
mkdir -p ~/.claude/skills
cp -R /tmp/legacy-to-ai-ready-src/.claude/skills/legacy-to-ai-ready ~/.claude/skills/legacy-to-ai-ready
# Requires python3 (stdlib only) to run scripts/analyze_codebase.py [project-path].
# Bundled assets/ include skill-creator, skill-downloader, resource-scout and CLAUDE.md/settings.json templates.

Skills live in ~/.claude/skills/ (global) or .claude/skills/ (per-project). Restart Claude Code after installing.

Commands — how to trigger Legacy To AI Ready

/legacy-to-ai-ready Analyzes an existing codebase and generates CLAUDE.md and Claude Code config

It also activates on plain-language prompts like these:

Make this old project AI-ready
Generate a CLAUDE.md for this legacy codebase
Create coding standards for AI on this repo

Frequently asked questions

Is the Legacy To AI Ready skill free?: Yes. The skill itself is free from nicepkg/ai-workflow. SkillProof publishes the install command and an independent test verdict at no cost.
Does Legacy To AI Ready work with Claude Code?: We tested it with Claude Code 2.x (agent harness) on Jul 31, 2026. Verdict: Tested · Works. Fetched SKILL.md (frontmatter parses, name+description present) and spot-checked 4 referenced files raw: analyze_codebase.py, claude-md-patterns.md, resource-discovery.md, CLAUDE.md.template all HTTP 200. Ran the 969-line analyze_codebase.py (syntax OK, only stdlib; sole subprocess call is `git log` to detect commit patterns, no exfiltration/curl|sh) against a real TS test project I built: it correctly detected TypeScript/Jest/ESLint/Prettier, extracted build/test/lint scripts, flagged conventional-commits from git history, warned about .env, and recommended a commit.md command. Wrote a baseline CLAUDE.md from general knowledge vs a skill-followed one using the script output + template: the skill version uniquely captured the conventional-commit convention, the .env/.claudeignore security note, prettier config values, and a follow-up commands recommendation the baseline entirely missed.
What is the Legacy To AI Ready SkillProof Score?: 8.8/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 7/10, docs & honesty 5/5.
How do I install Legacy To AI Ready?: Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use Legacy To AI Ready with Cursor, Copilot, Gemini CLI, Codex or other AI tools?: The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.